[thelist] SQL - Foreign Key Constraint - in another database?

Warden, Matt mwarden at mattwarden.com
Sat Sep 1 17:46:22 CDT 2001


>Establish naming conventions for your databases, and ensure that all
>databases, fields, tables, stored procedures, etc. conform. It helps with
>the portability and reusability of code and data, and is a bit of a memory
>aid; when you know, for instance, that tables are always named in the
>plural, you don't have to struggle to remember if it was 'employee' or
>'employees' and can focus on the task rather than the minutiae.


Ewww... that naming convention is not needed because table names should
never be plural. They don't need to be. Tables have multiple records, so
a 'table' implies the plural anyways.

So:

create table EMPLOYEE
(
...
);

implies that the table will hold multiple employees. Singlular table names
are so much nicer than plural (is that CATEGORYS or CATEGORIES? OCTOPUSSES
or OCTOPI? FISHES or FISH?).

Not that everyone follows this. Hell, even the evolt database has plurals
in some instances.


I'd show you a diagram of the evolt db, but it's pretty out of date. And,
no, this isn't a subtle prod, rudy  =)

</soapbox>


thanks,

--
mattwarden
mattwarden.com





More information about the thelist mailing list