Re: no meaningful way to determine fe or be version?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: aoki(at)acm(dot)org, pgsql-bugs(at)postgresql(dot)org
Subject: Re: no meaningful way to determine fe or be version?
Date: 2000-11-16 04:57:17
Message-ID: 200011160457.XAA25522@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

You can do a 'SELECT version()' to get a version string from the
backend.

> Paul M. Aoki (aoki(at)acm(dot)org) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> no meaningful way to determine fe or be version?
>
> Long Description
> both the odbc and jdbc drivers seem to hardcode the database version, e.g., org/postgresql/jdbc2/DatabaseMetaData.java always returns "6.5.2" when you call getDatabaseProductVersion().
>
> it would be nice if the metadata routines were actually tied to something returned from the backend.
>
> Sample Code
>
>
> No file was uploaded with this report
>
>

--
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

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2000-11-16 08:02:57 FOREIGN KEY check needs UPDATE permission
Previous Message Tom Lane 2000-11-15 17:45:08 WHERE-clause evaluation order (was Problem with BETWEEN and a view)