| From: | "Wappler, Robert" <rwappler(at)ophardt(dot)com> |
|---|---|
| To: | "John Gage" <jsmgage(at)numericable(dot)fr>, "Richard Huxton" <dev(at)archonet(dot)com> |
| Cc: | "Scott Mead" <scott(dot)lists(at)enterprisedb(dot)com>, "Postgres General Postgres General" <pgsql-general(at)postgresql(dot)org>, "pgAdmin Support List" <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] Byte order mark added by (the envelope please...) pgAdmin3 !! |
| Date: | 2010-04-22 09:25:12 |
| Message-ID: | C8E2DAF0E663A948840B04023E0DE32A027AA3A1@w2k3server02.de.ophardt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-general |
On 2010-04-22, John Gage wrote:
> Well, well, well. Guess who the culprit is...
>
> I edited the file both in Vim and in pgAdmin3 (1.10.2, Mar 9
> 2010, rev
> 8217), and the BOM shows up after saving the file with pgAdmin3.
>
> I don't know if pgAdmin3 wants to keep this feature...
>
> Thank everyone again for the excellent help.
>
> John
>
I do not think that it is a feature. Instead I think it is a bug in the
query parser. The BOM is a non-breakable space character. Leading space
characters should not harm.
--
Robert...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Gage | 2010-04-22 09:41:22 | Re: [GENERAL] Byte order mark added by (the envelope please...) pgAdmin3 !! |
| Previous Message | Vikram A | 2010-04-22 09:21:48 | Replication in postgresql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2010-04-22 09:26:48 | Getting the typename of a polymorphic function's magical $0 variable |
| Previous Message | John Gage | 2010-04-22 09:10:18 | Byte order mark added by (the envelope please...) pgAdmin3 !! |