You have already gone a long way to describing your table structure by
describing your data elements and their relationships to each other. Let
me try to summarize you descriptions and see if I can show you how to
translate your text descriptions into table descriptions.
1. There are things
On Oct 19, 2004, at 10:17 AM, [EMAIL PROTECTED] wrote:
You have already gone a long way to describing your table structure by
describing your data elements and their relationships to each other.
Let me try to summarize you descriptions and see if I can show you
how to translate your text
Timothy Luoma [EMAIL PROTECTED] wrote on 10/19/2004 11:11:12 AM:
On Oct 19, 2004, at 10:17 AM, [EMAIL PROTECTED] wrote:
You have already gone a long way to describing your table structure by
describing your data elements and their relationships to each other.
Let me try to
I have been tinkering with MySQL long enough to suit what modest needs
I have had, but now I need to setup a new DB that is going to have more
information in it, and I want to make sure that I am doing it the most
efficient way for the long term.
Surprisingly, I have not been able to find a
There are numerous advantages to going with the multiple table database
you described. That is what we call a normalized data structure. Try
searching again for terms like normalized, normalizing, and normal
form for additional background. Add the terms tutorial, or overview
to find web sites
Timothy,
Definately follow the advice that Shawn gave you. Doing it this way
will make it easy to have any number of emails per person without have
to know how many beforehand
. Here's an example below:
Table USERS:
userid=15
fname='Timothy'
lname='Luoma'
Table EMAILS:
userid=15
Ok, this makes a lot of sense now. (As usual, what seems like more
work initially pays off in the end.)
Here's a specific question.
The parent project is called TiM. We will, at times, want to pull
out information for *everyone*. But more often we will want to pull
out information just from
On Mon, 18 Oct 2004 17:49:22 -0400, Timothy Luoma [EMAIL PROTECTED] wrote:
Ok, this makes a lot of sense now. (As usual, what seems like more
work initially pays off in the end.)
Here's a specific question.
The parent project is called TiM. We will, at times, want to pull
out
