> Ok, I think I am understanding. So are you saying that I will need
another
> table if this is the case? Say I have antiques and collectible and it
has
> a
> sub_category of furniture. Since not all furniture is antique or
> collectible
> would that require another table?
Exactly. Instead of defi
> >As someone previously stated, the major drawback to this
> >design is that you can only have one parent for each item. If you
need
> >an item to have more than one parent, you would have to develop a two
> >table design.
>
> I can't imagine a scenario where I would need to have a single child
: "Doug Boude (rhymes with 'loud')" <[EMAIL PROTECTED]>
To: "CF-Talk"
Sent: Monday, August 21, 2006 3:33 PM
Subject: Re: Database design question
> >
> >
> >
> >- Original Message -
> >From: "Michael E. Carluen"
ve to be creating X number of tables to support my relationships.
two more cents for the pot.
>
>Hope that clears things up a bit.
>
>Rich Kroll
>
>-Original Message-
>From: Doug Brown [mailto:[EMAIL PROTECTED]
>Sent: Monday, August 21, 2006 3:26 PM
>To: CF-Talk
>
-
From: "Doug Bezona" <[EMAIL PROTECTED]>
To: "CF-Talk"
Sent: Monday, August 21, 2006 12:43 PM
Subject: RE: Database design question
> This is going to be a bit tricky to explain without diagrams, but I'll
> try and hope it's reasonably clear.
>
> One
No, only one table. I believe Doug Bezona and I are suggesting an identical
approach (so you now have a consensus solution).
> -Original Message-
> From: Doug Brown [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 21, 2006 12:26 PM
> To: CF-Talk
> Subject: Re: Database
]
sub_cat_category
Thanks for the help again.
- Original Message -
From: "Doug Bezona" <[EMAIL PROTECTED]>
To: "CF-Talk"
Sent: Monday, August 21, 2006 12:43 PM
Subject: RE: Database design question
> This is going to be a bit tricky to explain without diag
: Doug Brown [mailto:[EMAIL PROTECTED]
Sent: Monday, August 21, 2006 3:26 PM
To: CF-Talk
Subject: Re: Database design question
Thanks michael, but if I do it that way, will I not have hundreds of
tables?
I currently have about 24 categories and each category has prob 10-50
sub_categories and then each
n" <[EMAIL PROTECTED]>
To: "CF-Talk"
Sent: Monday, August 21, 2006 12:53 PM
Subject: RE: Database design question
> Doug, yYou can actually use a single table for that. One way is to create
a
> field that serves as a "parent_id".
>
> Example:
>
> ID:
for the help again.
- Original Message -
From: "Doug Bezona" <[EMAIL PROTECTED]>
To: "CF-Talk"
Sent: Monday, August 21, 2006 12:43 PM
Subject: RE: Database design question
> This is going to be a bit tricky to explain without diagrams, but I'll
&g
Doug, yYou can actually use a single table for that. One way is to create a
field that serves as a "parent_id".
Example:
ID: 1, NAME: Antiques and Vintages, PARENT_ID: 0
ID: 2, NAME: Antique Furniture, PARENT_ID: 1
ID: 3, NAME: Vintage Cars, PARENT_ID: 1
ID: 4, NAME: Hutches, PARENT_ID: 2
ID: 5,
This is going to be a bit tricky to explain without diagrams, but I'll
try and hope it's reasonably clear.
One approach is use a single category table that is self-referential.
For example, a table named category, with a categoryid, and a parentid.
Parentid would be a foreign key relationship to
Hey Doug... I know this isn't a direct answer to your question, but
something for the future - - get this book... it made everything pretty
clear for relational databases:
Database Design for Mere Mortals . . by Michael Hernandez
-Original Message-
From: Doug Brown [mailto:[EMAIL PROTECTE
To me the table structure looks fine, it would be one line per classified
ad.
If they can place more than one ad at a time, it wouldn't matter to the
database. You would write your scripts to allow for multiple instances of
ads and then submit them through a loop, inserting them one at a time.
> But what if you need read/write access? How transactional would
> that be?
In the SAP example cited, write access is not allowed. By that, I mean that
granting users (besides those used by the SAP/R3 system) write access to the
database voids your support contract. How's that for side stepping t
Ben Rogers wrote:
>
> I assume this goes for cross-server queries as well (such as linked servers
> in SQL Server)?
Of course implementations differ, but in general I consider
cross-database and cross-server queries something you use because
you *have* to, not because you *want* to.
> Well, s
I do use a database link on my current project to another server
sitting in the same server room. Unfortunately the columns that we
need to query on are not indexed on that box and to pull out records
takes for ever. If it did not it would be nice to just write the
queries to join our tables off
> In theory joining cross databases is not supported in the SQL
> standard. Therefore not every dbms will implement it, or they
> will require you to use clumsy workarounds.
I assume this goes for cross-server queries as well (such as linked servers
in SQL Server)?
> I find it hard to see the adv
Scott Mulholland wrote:
> In theory is there any downside to joining cross database.
In theory joining cross databases is not supported in the SQL
standard. Therefore not every dbms will implement it, or they
will require you to use clumsy workarounds.
I find it hard to see the advantages when
Oops. I meant to say "there are many reasons why you _can't_ limit
everything to a single database".
-Original Message-
From: Dawson, Michael [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 20, 2004 9:46 PM
To: CF-Talk
Subject: RE: Database design question
I do it al
I do it all the time, but I don't really like it. However, there are
many reasons why you can limit everything to a single database.
When I write a SQL statement, I ALWAYS use fully-qualified table names
such as:
databaseName.dbo.tableName
I do this even if I'm in the default database specified
data seperated for organization I can't find any benefit to having
them be 2 databases.
-Original Message-
From: Michael Traher [mailto:[EMAIL PROTECTED]
Sent: Friday, November 19, 2004 11:22 AM
To: CF-Talk
Subject: Re: Database design question
Well if you need multiple users data -
If you had multiple projects that all had their own databases but need
a central database for user authentication. We had something like
this years ago when I was working for the University. The IT
department did finally get a LDAP solution working correctly and that
is when we switched to that i
OTECTED]
> Sent: Friday, November 19, 2004 10:21 AM
> To: CF-Talk
> Subject: Re: Database design question
>
> In reality would you not tend to only need to read the user data at
> login time and then cache whatever user data is required (in a
> persistant scope of some ty
> In reality would you not tend to only need to read the
> user data at
> login time and then cache whatever user data is required
> (in a
> persistant scope of some type) so that your example would
> become
Not necessarily... if there is an administrative tool to manage users,
it might need to cr
by a specific user. Am I misinterpretting it?
-Original Message-
From: Michael Traher [mailto:[EMAIL PROTECTED]
Sent: Friday, November 19, 2004 10:21 AM
To: CF-Talk
Subject: Re: Database design question
In reality would you not tend to only need to read the user data at
login time and
In reality would you not tend to only need to read the user data at
login time and then cache whatever user data is required (in a
persistant scope of some type) so that your example would become
select a.title, u.firstname, u.lastname
from articles a
WHERE a.insertby = #request.account_id#
asi
- Original Message -
From: Bruce, Rodney S HQISEC/Veridian IT Services
To: CF-Talk
Sent: Thursday, November 21, 2002 3:34 PM
Subject: RE: Database design question
Janine
one question: would the goals be the same for all the students?
I would go with 3 tables
1. Student info
Janine
one question: would the goals be the same for all the students?
I would go with 3 tables
1. Student info
2. Goal info
3. link table with fk from student/goal tables and comments(grades)
something like
Table1
Studentid StudentName
Table2
Goalid GoalName
Table3
Studen
I would probably go for the 3-table layout.
First, if the goals are more typically graded 1 or 2 times per year, it
doesn't leave you with lots of wasted space for storing those grades,
comments, whatever.
Second, there's always the possibility that someone might need more -- for
example, a singl
Hello Kola Oyedeji,
Oops..It was Order detail Table.rather than order table
Regards
Nagaraj.A
- Original Message -
From: "Kola Oyedeji" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Monday, April 01, 2002 6:08 AM
Subject: OT: database design question re:product price chang
Hi Kola Oyedeji,
You Can Store the Product Price in orders table as it will save you from
making joins which is more overhead then
querying same table and having the prices in it.
With Regards
Nagaraj.A
- Original Message -
From: "Kola Oyedeji" <[EMAIL PROTECTED]>
To: "CF-Talk" <[E
If you have 3 tables, then there is no performance impact. I'd keep it
normalized.
-Original Message-
From: Koo Pai Lao [mailto:[EMAIL PROTECTED]]
Sent: October 5, 2001 4:54 PM
To: CF-Talk
Subject: Database Design Question
ok, this is just a small example of what I am working with.
I
The technique I was alluding to is called the Entity-Relationship (ER)
model. Do a search at your favorite book site, and you will find a bunch of
books on it.
~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusio
consider
> putting the answers in one row for each exam like ABBCCCBBDDEEBDD, then
just
> use some string functions on them!
>
>
> >From: "Pete Freitag" <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: CF-Talk <[EMAIL PROTECTED]>
> >S
EEBDD, then just
use some string functions on them!
>From: "Pete Freitag" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: CF-Talk <[EMAIL PROTECTED]>
>Subject: RE: Database Design Question
>Date: Mon, 21 May 2001 13:10:13 -0400
>
>Your DB can
Your DB can "probably" handle that many rows as long as its properly
indexed, but you should look at some database normalization techniques. A
fully normalized design might have a table for...
exams
questions
choices
the correct answer should be a foreign key in questions table to the choices
t
If you want to store all of the answers (not just the correct one) for each
question, I think you're actually looking at 3 tables:
tblExam - ExamId(PK), ExamName, ExamDate, etc.
tblQuestion - QuestionID(PK), ExamId(FK), QuestionText, etc.
tblAnswer - AnswerId(PK), QuestionID(FK), AnswerText, IsCo
First 12.5k rows is not very many. I've worked on SQL Server apps with
closer to 1 million rows. If you index the tables correctly and run
reasonable queries, I'd be surprised if you taxed the server too much.
As an alternate strategy though, you could do this with one table. Just
create a field
ROTECTED]]
Sent: Friday, March 30, 2001 1:05 PM
To: CF-Talk
Subject: Re: database design question
Well, as a Web Database programmer at UPS who works with
Access tables a great deal, when used as an interface with ColdFusion,
you can have up to 15 tables all supporting your websites with no
down
why only up to 15 tables?
"Julia Green" <[EMAIL PROTECTED]> wrote:
Well, as a Web Database programmer at UPS who works with
Access tables a great deal, when used as an interface with ColdFusion,
you can have up to 15 tables all supporting your websites with no
down time.
Usually people want only
Well, as a Web Database programmer at UPS who works with
Access tables a great deal, when used as an interface with ColdFusion,
you can have up to 15 tables all supporting your websites with no
down time.
Usually people want only functional tables, so they can export
them to the server a little f
ght. it said GRADUATED FROM. i've never known of
> anyone who has graduated from more than one high school :P
>
> - Original Message -
> From: Tony Schreiber <[EMAIL PROTECTED]>
> To: CF-Talk <[EMAIL PROTECTED]>
> Sent: Wednesday, March 28, 2001 10:36 PM
>
grr!! it does fit in right. it said GRADUATED FROM. i've never known of
anyone who has graduated from more than one high school :P
- Original Message -
From: Tony Schreiber <[EMAIL PROTECTED]>
To: CF-Talk <[EMAIL PROTECTED]>
Sent: Wednesday, March 28, 2001 10:36 PM
Subj
I think your highschoolrelations table is overkill when there is only a
1-1 relationship. If there were a small, finite number of schools, then
yes, a table of ids and names of those schools would be useful and you
would populate the highschool field of the user with that schools id. But
if there
While Juile obviously understands the idea of relational databases, I
think the question is more along the lines of balancing the number of
fields in a table with the number of tables you have. This is related to
the recent thread regarding, dang what was it?, well anyway, it's the same
thing.
If
An excellent on designing relational databases is Database Design for Mere
Mortals by Michael J. Hernandez. It has definitely helped me.
Judith
Julie Clegg put into words:
>hello,
>
>I am putting together a database and I cannot decide what to do with the
>Education Table. I have 1000 clients
Here is the question. Diod they graduate from high school? If so, which
high school?
Here is the inference.
Those who have a high school name went to high school, and those who didn't
have a high school name did not go to high school. i know it's a big DUH,
but it's important.
here's how i
time for a book on relational databases
Terry Bader
IT/Web Specialist
EDO Corp - Combat Systems
(757) 424-1004 ext 361 - Work
[EMAIL PROTECTED]
(757)581-5981 - Mobile
[EMAIL PROTECTED]
icq: 5202487 aim: lv2bounce
re in line below:
- Original Message -
From: "Jeffry Houser" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, November 16, 2000 9:36 PM
Subject: Re: Database design question
>
> I consider this type of topic my forte,
I consider this type of topic my forte, so I hope I can help.
Although, not a CF-specific question, I think this definitely
is something anyone should know before even starting to code in
ColdFusion.
> We are writing an application part of which handles scheduling of "classes"
> and "teache
I wanted to add that if you're using Oracle,
it natively supports recursive queries without
resorting to a recursive or looping function.
I don't remember the syntax (I'm working with
SQLServer now and don't have any Oracle
references at hand), but you can write what
is basically a standard SQL st
(740) 597-2524
- Original Message -
From: Dan G. Switzer, II <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 21, 2000 10:04 AM
Subject: RE: Database Design Question
> Brook,
>
> I'd recommend buying SQL for Smarties by Joe Celko. There's
Brook,
I'd recommend buying SQL for Smarties by Joe Celko. There's a couple of
chapter specifically on ways to handle hierarchy data w/different database
systems. I really like the "Nested-Set Model." The nice thing about the
Nested-Set model is that you can do all your tree parsing/order via SQL
-- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 21, 2000 12:23 PM
Subject: RE: Database Design Question
> The standard way to take care of this is a self-referencing table, and a
> recursive function to bust them out.
>
> ID|P
The standard way to take care of this is a self-referencing table, and a
recursive function to bust them out.
ID|Parent_ID
Top levels have an id of 0, and the other rows work well with an autonumber
in the id.
If children can have multiple parents, as in a BOM(Bill of Materials)
problem, you'll
The typical way of defining this is:
CREATE TABLE Category
(
CategoryID Integer Identity Primary Key,
DescriptionVarChar(255),
ParentCategoryID Integer References Category,
)
You will probably want to add an index on ParentCategoryID
Then you can expa
Brook,
Check out this article on using recursion at the Defusion site:
http://www.defusion.com/articles/index.cfm?ArticleID=63
I've used this setup in my Amazon partner bookstore where I have
categories and subcategories. Works well. See
http://www.astutia.com/books/index.cfm for an example.
58 matches
Mail list logo
