Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Convert PGconn, PGresult to opaque types?

From: Goran Thyni <goran(at)bildbasen(dot)se>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-interfaces(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Convert PGconn, PGresult to opaque types?
Date: 1998-08-24 12:50:51
Message-ID: (view raw or whole thread)
Lists: pgsql-hackerspgsql-interfaces
Bruce Momjian wrote:
> > Basically this would force applications to use the accessor functions
> > as recommended in the documentation, and not touch fields of a PGconn
> > object directly.  (Ditto for PGresult.)
> I am scared about external stuff like php.  If they use it, and we
> release something that doesn't work with their stuff, we are cooked
> until they upgrade.
> Not really sure what the advantage would be, aside from cleanliness.

The cleaness allows us to change the interals without breaking "external
I think Tom is aiming for thread-safeness which can't be done as long as
external stuff insists on accessing global structs inside libpq.
Sometimes we have to break thing to make them work better.

Göran Thyni, sysadm, JMS Bildbasen, Kiruna

In response to

pgsql-hackers by date

Next:From: Andreas ZeugswetterDate: 1998-08-24 12:54:08
Subject: USE_LOCALE and unsigned char *
Previous:From: David HartwigDate: 1998-08-24 12:38:51
Subject: Re: [HACKERS] Regression test status (was type coersion)

pgsql-interfaces by date

Next:From: Eric MarsdenDate: 1998-08-24 13:40:25
Subject: Re: [INTERFACES] JDBC Connection
Previous:From: Dr. HerreraDate: 1998-08-24 12:14:04
Subject: JDBC Connection

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group