From: Tom Lane <tgl@sss.pgh.pa.us>
To: Roger Hand <RHand@kailea.com>
Cc: Jim C. Nasby <jnasby@pervasive.com>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: R, Rajesh (STSD) <rajesh.r2@hp.com>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: [HACKERS] Query in SQL statement
Date: Sat, 01 Oct 2005 17:15:25 -0400
Message-ID: <28302.1128201325@sss.pgh.pa.us> (raw)
In-Reply-To: <DB28E9B548192448A4E8C8A3C1B1E475611D35@sj1-exch-01.us.corp.kailea.com>
References: <DB28E9B548192448A4E8C8A3C1B1E475611D35@sj1-exch-01.us.corp.kailea.com>
"Roger Hand" <RHand@kailea.com> writes:
>> I suggest ditching the CamelCase and going with underline_seperators.
>> I'd also not use the bareword id, instead using bad_user_id. And I'd
>> name the table bad_user. But that's just me. :)
> I converted a db from MS SQL, where tables and fields were CamelCase, and
> just lowercased the ddl to create the tables.
> So table and fields names were all created in lowercase, but I didn't have to change
> any of the application code: the SELECT statements worked fine with mixed case.
Yeah, the only time this stuff really bites you is if the application
sometimes double-quotes mixed-case names and sometimes doesn't. If it's
consistent then you don't have an issue ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, RHand@kailea.com, jnasby@pervasive.com, chriskl@familyhealth.com.au, rajesh.r2@hp.com, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Query in SQL statement
In-Reply-To: <28302.1128201325@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox