Bruce Momjian 7ee7ee1398 BLOBs containing NUL characters (ASCII 0) can be written to the ... database, but they get truncated at the first NUL by lo_read when they are read back. The reason for this is that lo_read in Pg.xs is using the default: OUTPUT: RETVAL buf which uses C's strlen() to work out the length of the scalar. The code ought to read something more like: OUTPUT: RETVAL buf sv_setpvn((SV*)ST(2), buf, RETVAL); I am not sure if this needs to be done on both lo_read methods in this file, but I changed both and have not since had any problems with truncated BLOBs. Douglas Thomson <dougt@mugc.cc.monash.edu.au>		1999-10-13 02:26:37 +00:00
..
cli	Incorporate fixes from Date and Darwen, 1997.	1999-06-18 05:03:48 +00:00
ecpg	*** empty log message ***	1999-10-08 11:05:05 +00:00
jdbc	jdbc2real rule was in there twice. One of them should have been jdbc1real	1999-09-15 21:56:16 +00:00
libpgeasy	Update pgeasy for missing files.	1999-10-12 14:06:49 +00:00
libpgtcl	Add pginterface into main tree, called pgeasy.	1999-10-11 17:47:02 +00:00
libpq	Add pginterface into main tree, called pgeasy.	1999-10-11 17:47:02 +00:00
libpq++	CmdTuples() returns an int showing the number of affected tuples after an	1999-10-06 03:00:16 +00:00
odbc	driver v06-40-0007	1999-09-03 05:29:00 +00:00
perl5	BLOBs containing NUL characters (ASCII 0) can be written to the	1999-10-13 02:26:37 +00:00
python	Update pygresql version stamp.	1999-05-28 04:54:34 +00:00
Makefile	Update again.	1999-10-11 18:05:39 +00:00