| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-jdbc(at)postgresql(dot)org>, <peter(at)retep(dot)org(dot)uk> |
| Subject: | Re: Displaying/Pulling Images using JDBC ... |
| Date: | 2001-05-12 18:55:29 |
| Message-ID: | Pine.BSF.4.33.0105121554530.629-100000@mobile.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Sat, 12 May 2001, Tom Lane wrote:
> The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> > Now, my thought on this is that it *sounds* like the JDBC is
> > hitting some sort of control character is the stream that tells it to stop
> > sending the image ... is this possible? Some binary character that needs
> > to somehow be trapped?
>
> Embedded nulls would be the likely cause of trouble.
>
> If you're seeing OIDs in the database then the actual storage is
> presumably in large objects. lo_read and friends are null-safe as far
> as I know; probably the problem is somewhere inside the JDBC driver.
that's kinda what I'm figuring too ... the question is where, and is there
a suitable work around ;(
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2001-05-12 19:26:35 | Re: Displaying/Pulling Images using JDBC ... |
| Previous Message | Tom Lane | 2001-05-12 18:21:17 | Re: Displaying/Pulling Images using JDBC ... |