From: | Roman Neuhauser <neuhauser(at)sigpipe(dot)cz> |
---|---|
To: | teknokrat <teknokrat(at)yahoo(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Quotation marks in queries |
Date: | 2005-07-20 14:05:55 |
Message-ID: | 20050720140554.GA79549@isis.sigpipe.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
# teknokrat(at)yahoo(dot)com / 2005-07-20 12:43:48 +0100:
> Tony Caduto wrote:
> >The easiest solution is just not to use caps or spaces in your
> >table/object names, there is no advantage to doing so.
> >People just need to get over the fact that having caps in a name make it
> >easier to read.
> >
> >My Test Table should be my_test_table, the naming makes no difference
> >to the application using the table.
> >
> >Same thing with ordering of fields in a table, it makes no difference
> >other than for looks if the fields are in the order you want them
> >to be in.
> >
> >It is much more of a pain to qoute your sql than it is to have it look
> >nice.
> >
> >Just my 2 cents on the subject.
> >
>
> The problem we have is that we want to migrate to postgresql from our
> current sql server db, but the problem with caps requiring quotes around
> them makes this a far from easy migration.
Just so that it doesn't look like your problems are caused by
PostgreSQL: it is in accordance with SQL:1999, with the exception
that SQL says "fold to uppercase", but PostgreSQL folds to lowercase.
IOW, if you require that "table" <> "Table" <> "TABLE", then SQL is
the wrong langaue.
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991
From | Date | Subject | |
---|---|---|---|
Next Message | Rose, Juergen | 2005-07-20 14:49:26 | on delete rules on a view problem |
Previous Message | Scott Marlowe | 2005-07-20 13:58:06 | Re: Slow first query |