Re: [GENERAL] rationale behind quotes for camel case?

2011-06-29 Thread Vincent Veyron
Le mardi 28 juin 2011 à 11:09 -0500, dennis jenkins a écrit : Any suggestions on how to name tables when table names contain both multi-word nouns and mutli-table many-many mappings? [..] The real table names are normal English words with subjective meaning. Not sure what you mean by

[GENERAL] rationale behind quotes for camel case?

2011-06-28 Thread fluca1978
Hi all, first of all I'm not expressing any critique against the use of quotes for identifier expressed using camel case. However a lot of new postgresql users seems to be unhappy with the use of quotes for camel case identifiers, so I'd like to know what is the rationale behind it. I mean, is a

Re: [GENERAL] rationale behind quotes for camel case?

2011-06-28 Thread John R Pierce
On 06/28/11 2:12 AM, fluca1...@infinito.it wrote: Hi all, first of all I'm not expressing any critique against the use of quotes for identifier expressed using camel case. However a lot of new postgresql users seems to be unhappy with the use of quotes for camel case identifiers, so I'd like

Re: [GENERAL] rationale behind quotes for camel case?

2011-06-28 Thread Merlin Moncure
On Tue, Jun 28, 2011 at 4:12 AM, fluca1...@infinito.it wrote: Hi all, first of all I'm not expressing any critique against the use of quotes for identifier expressed using camel case. However a lot of new postgresql users seems to be unhappy with the use of quotes for camel case identifiers,

Re: [GENERAL] rationale behind quotes for camel case?

2011-06-28 Thread dennis jenkins
On Tue, Jun 28, 2011 at 8:43 AM, Merlin Moncure mmonc...@gmail.com wrote: The rebuttal to the above points is that the problem with not quoting is that your identifiers are folded to lower case on the server which can make them difficult to read in psql, pgadmin, etc. when outputted. This

Re: [GENERAL] rationale behind quotes for camel case?

2011-06-28 Thread Greg Smith
fluca1...@infinito.it wrote: first of all I'm not expressing any critique against the use of quotes for identifier expressed using camel case. However a lot of new postgresql users seems to be unhappy with the use of quotes for camel case identifiers, so I'd like to know what is the rationale

Re: [GENERAL] rationale behind quotes for camel case?

2011-06-28 Thread Karsten Hilbert
On Tue, Jun 28, 2011 at 11:09:52AM -0500, dennis jenkins wrote: Any suggestions on how to name tables when table names contain both multi-word nouns and mutli-table many-many mappings? Example: Suppose that I have a table called foo and another table called barBiz (or bar_biz if you

Re: [GENERAL] rationale behind quotes for camel case?

2011-06-28 Thread Scott Ribe
On Tue, Jun 28, 2011 at 11:09:52AM -0500, dennis jenkins wrote: Any suggestions on how to name tables when table names contain both multi-word nouns and mutli-table many-many mappings? Example: Suppose that I have a table called foo and another table called barBiz (or bar_biz if you

Re: [GENERAL] rationale behind quotes for camel case?

2011-06-28 Thread Andrew Sullivan
On Tue, Jun 28, 2011 at 04:00:42AM -0700, John R Pierce wrote: capitals (probably reflecting its 1980s IBM origins), but PG decided a long time ago to default to lower case, since the final result has the same effect. Well, it _sort of_ has the same effect. In a traditional SQL environment,

Re: [GENERAL] rationale behind quotes for camel case?

2011-06-28 Thread Greg Smith
On 06/28/2011 12:09 PM, dennis jenkins wrote: Example: Suppose that I have a table called foo and another table called barBiz (or bar_biz if you prefer). Further, both of these tables have a serial primary key. Now I want to create a third table that represents a many-to-many relationship