"Roger Hand" <[EMAIL PROTECTED]> 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 ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster