This appears to be fixed in 6.5.
> On Tue, Feb 02, 1999 at 07:33:48PM +0800, Vikrant Rathore wrote:
>
> > If your query is bigger than 8192 bytes then libpq simply truncates it
> > without giving any warning
>
> I've read that in the docs, too (while back, didn't try it out). I have
> to say, t
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Has this been fixed in 6.5 beta?
>> On Tue, Feb 02, 1999 at 07:33:48PM +0800, Vikrant Rathore wrote:
>>
If your query is bigger than 8192 bytes then libpq simply truncates it
without giving any warning
>>
>> I've read that in the docs, too (w
Has this been fixed in 6.5 beta?
> On Tue, Feb 02, 1999 at 07:33:48PM +0800, Vikrant Rathore wrote:
>
> > If your query is bigger than 8192 bytes then libpq simply truncates it
> > without giving any warning
>
> I've read that in the docs, too (while back, didn't try it out). I have
> to say, t
On Tue, Feb 02, 1999 at 07:33:48PM +0800, Vikrant Rathore wrote:
> If your query is bigger than 8192 bytes then libpq simply truncates it
> without giving any warning
I've read that in the docs, too (while back, didn't try it out). I have
to say, though, that I think this behaviouur is somewhat
Dear Samil,
If your query is bigger than 8192 bytes then libpq simply truncates it
without giving any warning
Vikrant Rathore
On Tue, 2 Feb 1999, Postgres GOD wrote:
>
> i would like to know what is the maximum attribute record that can class
> can accomodate.
>
> i'm having problem with on
i would like to know what is the maximum attribute record that can class
can accomodate.
i'm having problem with one of my table(class) it hangs-up during
insertion.
i'm using the libpq in my c script as the programming interface for
postgres.
samil buri.
