From: | Peter T Mount <psqlhack(at)maidast(dot)demon(dot)co(dot)uk> |
---|---|
To: | Phil Thompson <phil(at)river-bank(dot)demon(dot)co(dot)uk> |
Cc: | pgsql-hackers(at)hub(dot)org |
Subject: | Re: [HACKERS] Re: [QUESTIONS] full JDBC driver ? |
Date: | 1998-02-14 11:03:54 |
Message-ID: | Pine.LNX.3.95.980214105803.22823D-100000@maidast |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, 14 Feb 1998, Phil Thompson wrote:
> Peter T Mount wrote:
> >
> > On Thu, 12 Feb 1998, The Hermit Hacker wrote:
> >
> > > On Thu, 12 Feb 1998, Peter T Mount wrote:
> > >
> > > > Getting most of the rest of DatabaseMetaData is my main priority after 6.3
> > > > is released. However, there are some methods that cannot yet be
> > > > implemented because postgresql itself isn't yet up to it.
> > >
> > > Like?
>
> Isn't the "right" way to do this to implement the standard
> INFORMATION_SCHEMA, then all frontends have a decent model to work to?
>
> Phil
Possibly. Where possible, we have either default or assumed values where
there is no (visible) way of getting these values.
I did miss one bit out of the last post: There is a problem with
getColumnPrivileges(), in that it will never work while pg_user is not
readable by public.
I know that someone (vadim?) was trying to work out where to store the
passwords (other than in pg_user).
Anyhow, now I've finished the courses my employer keeps sending me on, I
can now spend more time on this ;-)
--
Peter T Mount petermount(at)earthling(dot)net or pmount(at)maidast(dot)demon(dot)co(dot)uk
Main Homepage: http://www.demon.co.uk/finder
Work Homepage: http://www.maidstone.gov.uk Work EMail: peter(at)maidstone(dot)gov(dot)uk
From | Date | Subject | |
---|---|---|---|
Next Message | Tom I Helbekkmo | 1998-02-14 12:34:15 | Re: [HACKERS] Re: [PORTS] v6.3 release ToDo list and supported ports |
Previous Message | Peter T Mount | 1998-02-14 10:54:29 | Re: [HACKERS] pgsql and threads don't match |