Re: [HACKERS] Large objects names - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] Large objects names
Date
Msg-id 199808062310.TAA19367@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] Large objects names  (Peter T Mount <peter@retep.org.uk>)
List pgsql-hackers
> On Thu, 6 Aug 1998, Bruce Momjian wrote:
>
> > > On Wed, 5 Aug 1998, Bruce Momjian wrote:
> > >
> > > > Currently, large objects are stored internally as xinv### and xinx###.
> > > >
> > > > I would like to rename this for 6.4 to be _lobject_### to prevent
> > > > namespace collisions, and make them clearer for administrators.
> > > >
> > > > However, this may cause problems for backward compatability for large
> > > > object users.  As I see there are going to be other new large object
> > > > things in 6.4, it may not be an issue.
> > > >
> > > > Is is OK to rename them internally?
> > >
> > > Shouldn't be a problem. JDBC does refer to the xin prefix with the
> > > getTables method, so it's simply a single change there.
> >
> > I am suggesting changes in later releases to older interfaces can
> > communicated with 6.4 without any problems.
>
> That sounds ok.

Yes.  Older odbc/java/psql interfaces still use the xinv pattern to
restrict table lists.  As new interfaces use relkind, I can then change
the internal name.
--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

pgsql-hackers by date:

Previous
From: Peter T Mount
Date:
Subject: Re: [HACKERS] Large objects names
Next
From: dg@informix.com (David Gould)
Date:
Subject: Re: [HACKERS] indexes and floats