Re: Max size for bytea type

From: "Do, Leon \(Leon\)" <leondo(at)alcatel-lucent(dot)com>
To: "Kris Jurka" <books(at)ejurka(dot)com>
Cc: "PostgreSQL JDBC" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Max size for bytea type
Date: 2007-02-05 15:59:11
Message-ID: D1EE06BA46B1E4449AF9A4F2FBEE18617C19E9@ILEXC2U01.ndc.lucent.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Yes, we need a TODO item on the bytea parser. We need to be able to
handle rainny scenarios when data is bad.

Thanks

Leon Do

> -----Original Message-----
> From: Kris Jurka [mailto:books(at)ejurka(dot)com]
> Sent: Thursday, February 01, 2007 1:32 PM
> To: Do, Leon (Leon)
> Cc: PostgreSQL JDBC
> Subject: Re: [JDBC] Max size for bytea type
>
>
>
> On Mon, 22 Jan 2007, Do, Leon (Leon) wrote:
>
> > Sorry, it is my mistake. It is wrong data type.
> >
>
> Still there is a TODO item here. The driver shouldn't bail
> out with an ArrayIndexOutOfBoundsException. It might be best
> to fail immediately for a getBytes call on something that
> isn't bytea data. It's conceivable that you there is bytea
> escaped data in a text field, but really, what are the odds
> (and use cases) of that?
>
> Kris Jurka
>
>

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message shahab 2007-02-05 16:37:48 <table name> is not mapped
Previous Message Kris Jurka 2007-02-05 15:28:30 Re: meta data domains ibatis abator etc