From: | Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> |
---|---|
To: | |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Quotation marks in queries |
Date: | 2005-07-14 14:50:54 |
Message-ID: | 42D67BCE.2010007@amsoftwaredesign.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
Tony
Relyea, Mike wrote:
>You only need to use quotes in your SQL statements if your table names
>in PostgreSQL contain any upper case letters. PostgreSQL automatically
>converts all of your SQL statements to lower case unless they're quoted.
>
>As an alternative to quoting in VB (assuming you're using Access as your
>FE), store your SQL in tables where you can quote it correctly instead
>of having to use " & chr(34) & " or """" every time you want to insert a
>quote in VB.
>
>Mike
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2005-07-14 14:53:33 | Re: To Postgres or not |
Previous Message | Leif Jensen | 2005-07-14 14:19:22 | Re: Recursive stored procedure in C. |