Apache OpenOffice (AOO) Bugzilla – Issue 18344
postresql native driver : blobs (large objects) the easy way
Last modified: 2008-07-20 12:06:37 UTC
Hello, I am not sure this is the right methodo of suggesting features to the new postgresql native driver. Please, if not, foward to the right people. I am struggling to use OpenOffice to deal with images on forms with postgresql backend through ODBC. The postgresql driver needs a new type , "lo", to work. In the new pg 7.3.x versions, the odbc team hint does not work anymore. Meanwhile, the postgresql-contrib package contains a "semi-official" large object "lo" implementation. It is elegant and solve the problem of orphaned files when an OID is deleted with a new type. I already tested this contrib using direct sql commands to insert and extract images into a postgresql database. OpenOffice can DISPLAY a previously inserted image on forms. But can not insert a new one. The postgresql-contrib "lo" implementation is a almost new "full" data type, using oid as references/pointers , allowing more easy driver implementation. Please, take a look at the postgresql-contrib "lo" code. It will make implementing blobs (large objects) much more easy. Regards. Andre Felipe
fs->jbu: sounds as if you should decide about this :)
change subcomponent to 'none'
add to CC
The PostgreSQL 8.2.0 documentation says that there is a "bytea" datatype that is used for implementing the capability of storing binary-only data. @andremachado: Does this data type satisfy your needs? In this context I encountered another problem, created follow-up issue 89685.
Hello, I will have to test against new postgresql versions. The "ea" data type can be used given a limitation at size. It is not a full blob solution, but works for many situations. Thanks! Andre Felipe
is it right to set this issue to worksforme?
or can we close it?
I think we can close this one since basic blob functionality is given.
closing