-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Well, yeah, since I've got a few active databases already, and they are
poorly designed: beginner's bad luck.
The thing I have questions about lately are keys: primary and foreign. If
you're going to make a primary key, does it always have to be a number? Can
it be a combination of letters and numbers? And when you're using a primary
key as a foreign key....well, that's not really a question (stream of
conciousness)....How do you determine where to split up information? Is there
a such thing as a primary table? I guess I'm thinking of this in a
heirarchical manner: there is a main table, with your most basic information,
then there's the other stuff. But is that right? Then I've got a question
about adding columns later on, after you've got so many records: how do you
add them? I realize you probably don't want to put them in a new column in a
primary table, but the whole key thing bugs me about creating the new table.
Is this where a foreign key would be useful? (in addition to the other uses
of foreign keys...)
And that's the tip of the iceberg, I know. But penguins know all about them.
;-)
Russell
On Saturday 02 March 2002 16:03 pm, you wrote:
> The world would be a much better place if more people knew about proper
> database design.
>
> Syd
>
> Derek Glidden wrote:
> > On Mon, 2002-02-25 at 12:06, Derek Glidden wrote:
> >
> > And now everyone knows a little more about database design than anyone
> > in their right mind should ever care to know. :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8gZ1cAqKGrvVshJQRApaSAJ9qE4PeuRhPU3aNtx+S/i8GbCsX+ACbB7wh
cYB/0bAr+hgyif0BYlKYFPs=
=bYgb
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 17:37:43 EDT