| From: | Lincoln Yeoh <lylyeoh(at)mecomb(dot)com> |
|---|---|
| To: | Marcin Inkielman <marn(at)wsisiz(dot)edu(dot)pl> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, postgres-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: index problem |
| Date: | 2000-06-07 00:54:00 |
| Message-ID: | 3.0.5.32.20000607085400.0087b550@pop.mecomb.po.my |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
At 10:53 AM 05-06-2000 +0200, Marcin Inkielman wrote:
>On Mon, 5 Jun 2000, Lincoln Yeoh wrote:
>I solved my problem simplier:
>
>drop index oceny_stud_numer_albumu_protokol_id;
>
>and
>
>drop index oceny_stud_numer_albumu_protokoloceny_stud;
>
>failed....
>
>
>so I used:
>
>drop index "oceny_stud_numer_albumu_protokoloceny_stud";
>and it worked for me 8-)))
I wonder why it worked tho. How does Postgresql treat stuff between double
quotes, especially regard to string length limits?
Yes I know it's in the source code somewhere, but it's also good to know
the official/intended behaviour vs the actual behaviour.
Cheerio,
Link.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | George Dau | 2000-06-07 01:30:29 | Are the subscription CDs version 7 |
| Previous Message | Daniel Mendyke | 2000-06-06 23:41:15 | Timestamp and compatiblity with MySQL |