From: | Peter Mount <peter(at)retep(dot)org(dot)uk> |
---|---|
To: | elieatallah(at)hotmail(dot)com, pgsql-bugs(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: select problem |
Date: | 2001-03-01 21:13:59 |
Message-ID: | 5.0.2.1.0.20010301211229.00a6e620@mail.retep.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
At 13:37 01/03/01 -0500, pgsql-bugs(at)postgresql(dot)org wrote:
>Elie Atallah (elieatallah(at)hotmail(dot)com) reports a bug with a severity of 2
>The lower the number the more severe it is.
>
>Short Description
>select problem
>
>Long Description
>I'm using JDBC as an interface.
>
>The select query will be dynamicly built. In some situation the query
>string can reach a big length of characters (per example: 33000
>characters) what postgresql doesn't accept.
>
>
>Question:
>Is there a limit for the query string?
>If yes witch one.
Under 7.1 there is no limit. However as JDBC's DatabaseMetaData expects to
return a value for a call, it's says 64K. However this shouldn't really
affect anything, it's just a returned value.
Pre 7.1 was limited to 8k.
These were backend limitations not JDBC.
Peter
From | Date | Subject | |
---|---|---|---|
Next Message | Joncheng Kuo | 2001-03-01 22:33:30 | Installation bug |
Previous Message | Peter Mount | 2001-03-01 21:12:15 | Re: jdbc1 compile problem still present in beta5 (java 1.1.8/freebsd 4.2-STABLE) |