| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, Chris Travers <chris(at)travelamericas(dot)com>, Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, "Aly S(dot)P Dharshi" <aly(dot)dharshi(at)telus(dot)net>, "Gavin M(dot) Roy" <gmr(at)ehpg(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL Gotchas |
| Date: | 2005-10-16 17:51:23 |
| Message-ID: | 9082.1129485083@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> Okay, how do we refer to the "RI_FKey_cascade_del" function then? Or
> trigger "RI_ConstraintTrigger_2204908". Using $$ quoting? Invent
> another quoting style?
Yeah, I was wondering about those myself. Probably we could just change
their names to something that could still be spelled. Or do nothing ---
I can't see any obvious reason why the average user would need to
reference those functions/triggers anyway, and if he did, he could turn
off the force-lowercase flag.
> Depends at what level you do the conversion. But lowercasing here means
> that people producing HTML tables using psql and providing multi word
> titles are going to be mightily disappointed if their titles are
> lowercased on them.
If they care about case, they wouldn't be turning this flag on anyway.
What we are looking for here is a simple, understandable hack that
solves 95% of the problem for legacy applications. Not something that
we'd encourage people to have on at all times.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-10-16 17:56:36 | Re: PostgreSQL Gotchas |
| Previous Message | Tom Lane | 2005-10-16 17:46:54 | Re: Long running update |