Ohlemeyer Matthias <[EMAIL PROTECTED]> writes: >> From: Daniel S. Haischt [mailto:[EMAIL PROTECTED]] ... >> i have read the postgresql jdbc driver on OID and bytea. >> >> as i understood both types are completly different ... >> >> - in best case OID is a pointer to a lob >> in worst case it is a pointer to an other type (INTEGER or sth.) >> >> the goid thing is that the client application >> is able to retrieve byte by byte of the lob >> (e.g. a stream) and not the whole lob at once. >> >> - bytea means that the client application retrieves >> the whole lob at once. that is the way the jdbc >> driver implements bytea. >> >> i found that info at ... >> >> -> http://lab.applinet.nl/postgresql-jdbc/#Lob >> >> sure, postgresql does have full index support. >> the point was that creates lots of indexes by >> itself. >> >> i do not know if that is the real reason, but >> the sql create script did not work out for me, >> if i kept the indexes. >> >> i have to figure out why the explicit index >> generation reports errors. >> >> i changed varchar(255) to text(1000) is that >> ok? >> >> btw - i just read this sentence on the postgresql's >> jdb driver page ... >> >> 'bytea is currently unsupported in the JDBC interface' > > This goes for PostgreSQL 7.1.x and before. You can use > bytea in 7.2 and the corresponding jdbc-driver. I have the > hope that this will circumvent a few problems. On the other > hand it would make the use of PostgreSQL 7.2 mandatory - but > then again there is a minimum version requirement for MySQL, too.
In that case, it looks like Torque will require PostgreSQL 7.2+ unless somebody comes up with a clever work around. Dan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
