| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Roger Hand" <RHand(at)kailea(dot)com> |
| Cc: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "R, Rajesh (STSD)" <rajesh(dot)r2(at)hp(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Query in SQL statement |
| Date: | 2005-10-01 21:15:25 |
| Message-ID: | 28302.1128201325@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
"Roger Hand" <RHand(at)kailea(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2005-10-01 21:54:27 | 8.1beta2 pg_dumpall inconsistencies |
| Previous Message | Tom Lane | 2005-10-01 21:13:40 | Re: [PATCHES] Proposed patch for sequence-renaming problems |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2005-10-01 21:56:07 | Re: [PERFORM] A Better External Sort? |
| Previous Message | AL ELK | 2005-10-01 20:08:31 | Which one FreeBSD or Linux |