Re: Status of server side Large Object support?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Thomas Hallgren <thhal(at)mailblocks(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Status of server side Large Object support?
Date: 2004-11-28 16:26:23
Message-ID: 41A9FC2F.3010504@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>The "inv_api" large objects are deprecated. CLOBs and BLOBs should be based
>on text and bytea, respectively.
>
>
Until bytea is actually useful with large scale binaries I would
say that large objects are far from deprecated. You can't reasonably
store large binary date in bytea.

Large objects are currently much more useful and easier to work with.

Sincerely,

Joshua D. Drake

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL

Attachment Content-Type Size
jd.vcf text/x-vcard 285 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2004-11-28 16:31:43 Re: Stopgap solution for table-size-estimate updating
Previous Message Bernd Helmle 2004-11-28 16:03:57 Re: Status of server side Large Object support?