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

Re: Connection.setCatalog()

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: jason(at)netspade(dot)com
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Connection.setCatalog()
Date: 2001-07-21 18:56:25
Message-ID: 200107211856.f6LIuPI01364@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-jdbc
Patch applied.  Thanks.

> [[[ Original Message from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> ]]]
> 
> > Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > > Tom Lane writes:
> > >> Peter E. has previously commented that Postgres databases correspond
> > >> most closely to the SQL concept of "catalog cluster", not "catalog".
> > 
> > > I most certainly did not.  According to my interpretation:
> > 
> > I sit corrected.  If you want to define catalog == database, okay with
> > me.
> > 
> > 			regards, tom lane
> 
> Great, here is a context diff of CVS for implementing the get/setCatalog methods in Connection - note: I've updated setCatalog(String catalog) from my previous diff so it checks whether it is already connected to the specified catalog.
> 
> Thanks,
> 
> Jason Davies
> 
> jason(at)netspade(dot)com

[ Attachment, skipping... ]

> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
> 
> http://www.postgresql.org/users-lounge/docs/faq.html

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

pgsql-jdbc by date

Next:From: Bruce MomjianDate: 2001-07-21 18:57:10
Subject: Re: DatabaseMetaData.getColumns() - default values
Previous:From: Bruce MomjianDate: 2001-07-21 18:52:22
Subject: Re: [PATCHES] Re: [PATCH] Cleanup of JDBC character encoding

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