Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-jdbc by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group