On Fri, Jan 31, 2003 at 11:33:35PM -0600, pgsql-general-owner+M37147=will=serensoft.com@postgresql.org wrote:
> On Fri, 31 Jan 2003 22:30:45 -0600, will trillich wrote:
> What you name your tables and columns should represent the data
> accurately. That way, when you hire a consultant, you don't have to pay
> him for the time he (or she) takes figuring out an arcane and
> non-representative naming scheme. And your successors will bless your
> name for intelligently naming you fields. :)
>
> As far as the data is concerned, Postgresql doesn't care what you call it.
> I think as long as you avoid keywords you'll be alright.
true.
you know how many time i wish i could use a "date" field? or
"on"? or "table"? :( (without having to use the blasted quotes,
of course...)
--
There are 10 kinds of people:
ones that get binary, and ones that don't.
will@serensoft.com
http://sourceforge.net/projects/newbiedoc -- we need your brain!
http://www.dontUthink.com/ -- your brain needs us!
Looking for a firewall? Do you think smoothwall sucks? You're
probably right... Try the folks at http://clarkconnect.org/ !
