From: Bruce Momjian <maillist@candle.pha.pa.us>
To: peter@retep.org.uk
Cc: hackers@postgreSQL.org
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] Large objects names
Date: Thu, 6 Aug 1998 19:10:49 -0400 (EDT)
Message-ID: <199808062310.TAA19367@candle.pha.pa.us> (raw)
In-Reply-To: <Pine.LNX.3.96.980806184229.793L-100000@maidast.retep.org.uk>
> 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)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: maillist@candle.pha.pa.us, peter@retep.org.uk, hackers@postgreSQL.org
Subject: Re: [HACKERS] Large objects names
In-Reply-To: <199808062310.TAA19367@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox