| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | Sergio Lob <sergio_lob(at)iwaysoftware(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: BUG #1523: precision column value returned from getTypeInfo() |
| Date: | 2005-03-04 03:06:54 |
| Message-ID: | Pine.BSO.4.56.0503032205140.25906@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-jdbc |
On Fri, 4 Mar 2005, Oliver Jowett wrote:
> > After calling Connection.DatabaseMetaData.getTypeInfo() method, the
> > PRECISION column of the ResultSet seems hardcoded to value 9, which of
> > course in incorrect
>
> Well, it's working as intended in the sense that there is no code to
> support retrieving a real precision value -- it is indeed a hardcoded
> placeholder value. I'm not sure why '9' off the top of my head, perhaps
> making that column NULL would be better? What are the units of this
> value anyway?
Compare the existing implementation of ResultSetMetaData.getPrecision.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis van Dok | 2005-03-04 10:17:14 | BUG #1524: drop view cascade deletes other user's views |
| Previous Message | Oliver Jowett | 2005-03-04 02:07:35 | Re: BUG #1523: precision column value returned from getTypeInfo() |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2005-03-04 06:55:59 | Re: DatabaseMetaData.getIndexInfo and function-based indexes |
| Previous Message | Oliver Jowett | 2005-03-04 02:07:35 | Re: BUG #1523: precision column value returned from getTypeInfo() |