| From: | "ADBAAMD" <adba(dot)amdocs(at)bell(dot)ca> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Cc: | "Brian T(dot) Allen" <brian(at)gzmarketing(dot)com>, "Shaw Terwilliger" <sterwill(at)sourcegear(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Database Name Case Sensitivity |
| Date: | 2001-04-06 16:03:40 |
| Message-ID: | 3ACDE8DC.8090703@bell.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-novice |
Peter Eisentraut wrote:
> ADBAAMD writes:
>
>> I think that's the issue. It is the old behaviour in pgsql, but not the
>> SQL standard one. For people coming from ANSI SQL (or some
>> approximation of it) as myself, this can be confusing.
>
> The behaviour in PostgreSQL *is* standard. There is no old behaviour.
> Which behaviour do you envision?
Then I misunderstood everything. As far as I understood, pgsql behaviour
differs from ANSI SQL in the identifier name's case issue. I really
understand that it is more convenient as it is, the issue is when you
migrate from Oracle or other ANSIsh SQL db.
--
Leandro
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Richter | 2001-04-06 16:12:34 | PostGreSQL 7.0.3 hangs in SuSE |
| Previous Message | Tom Lane | 2001-04-06 15:06:30 | Re: Can't recreate view from backup |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Byerley | 2001-04-06 17:59:41 | replacing tables |
| Previous Message | Peter Eisentraut | 2001-04-06 14:53:54 | Re: Database Name Case Sensitivity |