Thanks Shammat
Good to hear bytea works - am i correct in inferring that strings need to be reworked to ensure funny ascii sequences are not included? suppose
it's a text string - no problem. If it's an image that has a few contiguous bytes which are ascii 0 or ascii 255 what happens. An image may have
several hundred bytes like this. The manual says to use escape sequences
The LOB issue is serious. Any example code [any language] will help
I stored a few LOBs on localhost - was also able to retreive them
However the moment I am on another networked machine [ODBC] this fails
What's the hitch?
Here's the line from the manual
Large Objects (BLOBs)
Quote:
Full path names must be used with large objects because the database server runs in a different directory than the psql client. Files are imported and exported by the postgres user, so postgres must have permission to read the file for lo_import() and directory write permission for lo_export(). Because large objects use the local filesystem, users connecting over a network cannot use lo_import or lo_export(). They can, however, use psql's \lo_import and \lo_export commands.
What the dickens does this mean??
lo_write and lo_import does not work!
is another guy suffering. I'm heading for a minor 'eart attack
Anyways do let me know how successful your bytea is with binary strings with
peculiar non UTF-8 sequences.