Thread: underscore problem
Is there anywhere in the docs that says we should not use an underscore in a table name? table FC_Client_Info exists with a record where jobno 1234 has info: select acode from FC_Client_Info where jobno = '1234'; fails with a warning that fc_client_info does not exist notice the lower case. If I quote the table select acode from "FC_Client_Info" where jobno = '1234'; the select works fine What's the problem here? This should be easy. Ted
From: "postgresql" <pgsql@symcom.com> > Is there anywhere in the docs that says we should not use an > underscore in a table name? > > select acode from FC_Client_Info where jobno = '1234'; > fails with a warning that fc_client_info does not exist > notice the lower case. If I quote the table > > select acode from "FC_Client_Info" where jobno = '1234'; > the select works fine It's the case not the underscore. PG lower-cases table/field names both on creation and on queries. You can create/access mixed-case tables by quoting them, as you've discovered. This usually crops up converting from a different DB to Postgresql. - Richard Huxton
if your table is table name is case sensitive, you should double quota it, since postgres take lower case as default. Jie LIANG St. Bernard Software Internet Products Inc. 10350 Science Center Drive Suite 100, San Diego, CA 92121 Office:(858)320-4873 jliang@ipinc.com www.stbernard.com www.ipinc.com On Tue, 27 Feb 2001, postgresql wrote: > Is there anywhere in the docs that says we should not use an > underscore in a table name? > > table FC_Client_Info exists with a record where jobno 1234 has > info: > > select acode from FC_Client_Info where jobno = '1234'; > fails with a warning that fc_client_info does not exist > notice the lower case. If I quote the table > > select acode from "FC_Client_Info" where jobno = '1234'; > the select works fine > > What's the problem here? This should be easy. > > Ted > >