How difficult would it be to add a configuration option (at the global, database or session level) to make PostgreSQL transparently quote identifiers for you? That would be a simple way to allow users to use case-sensitive names without quoting everything manually or changing deep parts of the back end to support case insensitivity. I'd certainly welcome such a feature... 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 > > > > > -----Original Message----- > From: pgsql-general-owner@xxxxxxxxxxxxxx > [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Martynas > Brijunas > Sent: Thursday, July 14, 2005 3:32 AM > To: pgsql-general@xxxxxxxxxxxxxx > Subject: Quotation marks in queries > > Hello, > > I am a total newbie to PostgreSql, coming from MS Access background. I > have > a question regarding queries in PostgreSql: why do I need to enclose > every > field name and table name in quotation marks like > > SELECT "Name" From "contacts" > > That is a major inconvenience when composing a query string in a VB > program. > Thank you. > > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your > message can get through to the mailing list cleanly > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
