large object support in PostGres 7.4 - Mailing list pgsql-sql

From Vadivel Subramaniam
Subject large object support in PostGres 7.4
Date
Msg-id OF703A94D2.9C92140B-ON65257019.00220470-65257019.0022D0C7@flextronicssoftware.com
Whole thread Raw
Responses Re: large object support in PostGres 7.4
List pgsql-sql



Hi,

We have API's in /usr/local/pgsql/include/libpq-fe.h which support large
objects in PostGres     extern int  lo_open(PGconn *conn, Oid lobjId, int mode);     extern int  lo_close(PGconn *conn,
intfd);     extern int  lo_read(PGconn *conn, int fd, char *buf, size_t len);     extern int  lo_write(PGconn *conn,
intfd, char *buf, size_t len);     extern int  lo_lseek(PGconn *conn, int fd, int offset, int whence);     extern Oid
lo_creat(PGconn*conn, int mode);     extern int  lo_tell(PGconn *conn, int fd);     extern int  lo_unlink(PGconn *conn,
OidlobjId);     extern Oid  lo_import(PGconn *conn, const char *filename);     extern int  lo_export(PGconn *conn, Oid
lobjId,const char
 
*filename);

My doubt is, do these API's operate on character data?   i.e., My table
schema is like this

table (name varchar, script varchar).  I have to store a large data(in
character form) in the script column (upto 3 MB).

As of my understanding the above mentioned API's work on the OID field.
i.e,.  table(name varchar, script oid).  Is that correct?
Please clarify this if anyone has already used this large object APIs and
specify if this has any limitation on the size?

thanks,
-Vadivel



***********************  FSS-Private   ***********************
"DISCLAIMER: This message is proprietary to Flextronics Software Systems
Limited (FSS) and is intended solely for the use of the
individual to whom it is addressed. It may contain  privileged or
confidential information and should not be circulated or used for
any purpose other than for what it is intended. If you have received this
message in  error, please notify the originator immediately.
If you are not the intended recipient, you are notified that you are
strictly  prohibited  from  using, copying, altering, or disclosing
the contents of this message.  FSS  accepts no  responsibility  for loss or
damage arising from the use of  the information transmitted
by this email including damage from virus."



pgsql-sql by date:

Previous
From: Nick Johnson
Date:
Subject: Re: preventing deletion of a row
Next
From: Volkan YAZICI
Date:
Subject: Re: large object support in PostGres 7.4