Yes, we need a TODO item on the bytea parser. We need to be able to
handle rainny scenarios when data is bad.
> -----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
pgsql-jdbc by date
|Next:||From: shahab||Date: 2007-02-05 16:37:48|
|Subject: <table name> is not mapped|
|Previous:||From: Kris Jurka||Date: 2007-02-05 15:28:30|
|Subject: Re: meta data domains ibatis abator etc|