I'm on Ver16 and yes Our database has image in a bytea field. Running on Win22 box...
On Wed, Oct 16, 2024 at 5:49 PM Peter J. Holzer <hjp-pg...@hjp.at> wrote: > On 2024-10-16 16:02:24 -0400, Ron Johnson wrote: > > On Wed, Oct 16, 2024 at 4:00 PM Achilleas Mantzios < > > a.mantz...@cloud.gatewaynet.com> wrote: > > Στις 16/10/24 22:55, ο/η Ron Johnson έγραψε: > > On Wed, Oct 16, 2024 at 3:37 PM Andy Hartman < > hartman60h...@gmail.com> > > wrote: > [...] > > > > Step 1: redesign your DB to NOT use large objects. It's an old, > slow > > and unmaintained data type. The data type is what you should > use. > > > > You mean bytea I guess. As a side note, (not a fan of LOs), I had the > > impression that certain drivers such as the JDBC support streaming > for LOs > > but not for bytea? It's been a while I haven't hit the docs tho. > > > > > > Our database is stuffed with images in bytea fields. The Java > application uses > > JDBC and handles them just fine. > > Images are usually small enough (a few MB) that they don't need to be > streamed. > > I don't think bytea can be streamed in general. It's just like text, you > write and read the whole thing at once. > > If you have data which is too large for that and want to store it in > bytea fields, you'll probably have to chunk it yourself (which you > probably have to anyway because for me "so large it has to be streamed" > implies "at least possibly larger than 1 GB"). > > hp > > -- > _ | Peter J. Holzer | Story must make more sense than reality. > |_|_) | | > | | | h...@hjp.at | -- Charles Stross, "Creative writing > __/ | http://www.hjp.at/ | challenge!" >
