From: | Peter Mount <peter(at)retep(dot)org(dot)uk> |
---|---|
To: | <dbrown(at)pingtel(dot)com>, <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Bug #694: can't store {digits} using JDBC |
Date: | 2002-06-21 10:28:58 |
Message-ID: | Pine.LNX.4.33.0206211027060.6183-100000@sabrina.retep.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, 20 Jun 2002 pgsql-bugs(at)postgresql(dot)org wrote:
> Dan Brown (dbrown(at)pingtel(dot)com) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> can't store {digits} using JDBC
>
> Long Description We are using the JDBC driver, and are losing partial
> data. Whenever we try to store {digits} (note: exactly as shown with
> the curly brackets) we are finding that postgres is storing it as "
> igits ". We can insert it via psql correctly, but not via the JDBC
> driver. Also note, if we store something like {vdigits}, we have no
> problem. Also, it works fine in Oracle 8.
This is an escape syntax. {d refers to a date, which is why you are seeing
igits not {digits}.
Try the Statement.setEscapeProcessing() method to turn it off.
Peter
>
> The version of postgreSQL we are using is:
> PostgreSQL 7.2.1 on i686-pc-cygwin, compiled by GCC 2.95.3-5
> ( we are also seeing the same problem in Linux ).
>
> Sample Code
>
>
> No file was uploaded with this report
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
Peter T Mount
peter(at)retep(dot)org(dot)uk
http://www.retep.org.uk
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-06-21 14:02:51 | Re: [PATCHES] pg_dumpall should permit quiet operation |
Previous Message | Bruce Momjian | 2002-06-21 00:45:32 | Re: Patch for memory leaks in index scan |