>
>>lo: another special data type. Is its functionality required
>>anymore? It appears to be a workaround to some limitations of
>>our large object interface which may no longer exist.
I **think** the lo datatype is for ODBC binary access.
Sincerely,
Joshua D. Drake
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
