| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Sergio Lob <sergio_lob(at)iwaysoftware(dot)com> |
| Cc: | 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 02:07:35 |
| Message-ID: | 4227C2E7.7030308@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-jdbc |
(cc'ing -jdbc)
Sergio Lob 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?
If you're willing to do the implementation work to improve this, then
post a patch to pgsql-jdbc and I can look at applying it.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2005-03-04 03:06:54 | Re: BUG #1523: precision column value returned from getTypeInfo() |
| Previous Message | Sergio Lob | 2005-03-03 21:24:19 | BUG #1523: precision column value returned from getTypeInfo() always has value 9 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2005-03-04 03:06:54 | Re: BUG #1523: precision column value returned from getTypeInfo() |
| Previous Message | Sergio Lob | 2005-03-03 21:24:19 | BUG #1523: precision column value returned from getTypeInfo() always has value 9 |