Home > Archive > PostgreSQL JDBC > December 2005 > Re: large objects are "deprecated" ?









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Re: large objects are "deprecated" ?
Kris Jurka

2005-12-16, 1:23 pm

Marc Herbert wrote:
> Hi Kris,


Please send JDBC questions to the pgsql-jdbc@postgresql.org mailing
list, not any individual developers.

> doc/pgjdbc.xml, written by Peter Eisentraut. Concerning Large
> Objects, this document claims:
>
> PostgreSQL provides two distinct ways to store binary data. [in the
> table, or outside the table] In order to determine which method is
> appropriate you need to understand the limitations of each method....
>
> Peter himself says the opposite, at least that's what I understood from:
>
> http://permalink.gmane.org/gmane.co...resql.odbc/4971


Large objects are not deprecated. As the documentation claims there are
advantages and drawbacks to using each datatype. The decision of which
to use really revolves around how much data you intend to store.

Kris Jurka

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com