pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedLarge objects names
8+ messages / 3 participants
[nested] [flat]
* Large objects names
@ 1998-08-06 03:53 Bruce Momjian <maillist@candle.pha.pa.us>
0 siblings, 2 replies; 8+ messages in thread
From: Bruce Momjian @ 1998-08-06 03:53 UTC (permalink / raw)
To: hackers@postgreSQL.org
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?
--
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)
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: [HACKERS] Large objects names
@ 1998-08-06 05:27 Bruce Momjian <maillist@candle.pha.pa.us>
parent: Bruce Momjian <maillist@candle.pha.pa.us>
1 sibling, 0 replies; 8+ messages in thread
From: Bruce Momjian @ 1998-08-06 05:27 UTC (permalink / raw)
To: maillist@candle.pha.pa.us; +Cc: hackers@postgreSQL.org; pgsql-interfaces
> 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?
I will probably keep the current names for a few releases. Once
interfaces start using the relkind field to identify them, rather than
the xinv* naming, I will be able to change the names to anything else
and no external interface will care.
--
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)
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: [HACKERS] Large objects names
@ 1998-08-06 05:59 Peter T Mount <peter@retep.org.uk>
parent: Bruce Momjian <maillist@candle.pha.pa.us>
1 sibling, 3 replies; 8+ messages in thread
From: Peter T Mount @ 1998-08-06 05:59 UTC (permalink / raw)
To: Bruce Momjian <maillist@candle.pha.pa.us>; +Cc: PostgreSQL-development <hackers@postgresql.org>
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.
--
Peter T Mount peter@retep.org.uk or petermount@earthling.net
Main Homepage: http://www.retep.org.uk
PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: [HACKERS] Large objects names
@ 1998-08-06 13:14 David Hartwig <daveh@insightdist.com>
parent: Peter T Mount <peter@retep.org.uk>
2 siblings, 0 replies; 8+ messages in thread
From: David Hartwig @ 1998-08-06 13:14 UTC (permalink / raw)
To: Peter T Mount <peter@retep.org.uk>; +Cc: Bruce Momjian <maillist@candle.pha.pa.us>; PostgreSQL-development <hackers@postgreSQL.org>
Peter T Mount 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.
>
The same goes for ODBC.
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: [HACKERS] Large objects names
@ 1998-08-06 15:34 Bruce Momjian <maillist@candle.pha.pa.us>
parent: Peter T Mount <peter@retep.org.uk>
2 siblings, 0 replies; 8+ messages in thread
From: Bruce Momjian @ 1998-08-06 15:34 UTC (permalink / raw)
To: peter@retep.org.uk; +Cc: hackers@postgreSQL.org; pgsql-interfaces
> 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.
So does ODBC. Let's start using relkind = 'l', then I can change the
name in a later release, and no one will see the change.
--
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)
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: [HACKERS] Large objects names
@ 1998-08-06 15:35 Bruce Momjian <maillist@candle.pha.pa.us>
parent: Peter T Mount <peter@retep.org.uk>
2 siblings, 1 reply; 8+ messages in thread
From: Bruce Momjian @ 1998-08-06 15:35 UTC (permalink / raw)
To: peter@retep.org.uk; +Cc: hackers@postgreSQL.org; pgsql-interfaces
> 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.
--
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)
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: [HACKERS] Large objects names
@ 1998-08-06 17:42 Peter T Mount <peter@retep.org.uk>
parent: Bruce Momjian <maillist@candle.pha.pa.us>
0 siblings, 1 reply; 8+ messages in thread
From: Peter T Mount @ 1998-08-06 17:42 UTC (permalink / raw)
To: Bruce Momjian <maillist@candle.pha.pa.us>; +Cc: pgsql-interfaces
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.
--
Peter T Mount peter@retep.org.uk or petermount@earthling.net
Main Homepage: http://www.retep.org.uk
PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: [HACKERS] Large objects names
@ 1998-08-06 23:10 Bruce Momjian <maillist@candle.pha.pa.us>
parent: Peter T Mount <peter@retep.org.uk>
0 siblings, 0 replies; 8+ messages in thread
From: Bruce Momjian @ 1998-08-06 23:10 UTC (permalink / raw)
To: peter@retep.org.uk; +Cc: hackers@postgreSQL.org; pgsql-interfaces
> 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)
^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~1998-08-06 23:10 UTC | newest]
Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1998-08-06 03:53 Large objects names Bruce Momjian <maillist@candle.pha.pa.us>
1998-08-06 05:27 ` Bruce Momjian <maillist@candle.pha.pa.us>
1998-08-06 05:59 ` Peter T Mount <peter@retep.org.uk>
1998-08-06 13:14 ` David Hartwig <daveh@insightdist.com>
1998-08-06 15:34 ` Bruce Momjian <maillist@candle.pha.pa.us>
1998-08-06 15:35 ` Bruce Momjian <maillist@candle.pha.pa.us>
1998-08-06 17:42 ` Peter T Mount <peter@retep.org.uk>
1998-08-06 23:10 ` Bruce Momjian <maillist@candle.pha.pa.us>
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