pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dario V. Fassi <software@sistemat.com.ar>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Kris Jurka <books@ejurka.com>
Cc: pgsql-jdbc@postgresql.org
Cc: pgsql-bugs@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: [JDBC] Error in DatabaseMetaData.getColumns() with Views
Date: Sun, 04 Jul 2004 20:28:02 -0300
Message-ID: <40E89282.9060306@sistemat.com.ar> (raw)
In-Reply-To: <20040704153840.Y52747@megazone.bigpanda.com>
References: <40E6088E.6030703@yahoo.com.ar>
	<Pine.BSO.4.56.0407030343090.19721@leary.csoft.net>
	<40E6E7AF.5020306@sistemat.com.ar>
	<40E6FD7F.50801@sistemat.com.ar>
	<Pine.BSO.4.56.0407041330180.26773@leary.csoft.net>
	<20040704153840.Y52747@megazone.bigpanda.com>



Stephan Szabo wrote:

>On Sun, 4 Jul 2004, Kris Jurka wrote:
>
>  
>
>>On Sat, 3 Jul 2004, Dario V. Fassi wrote:
>>
>>    
>>
>>>In the sample adjunct, you can see that error arise at the time when the
>>>view's sql text is parsed and saved in database catalog.
>>>Then generic NUMERIC type is forced for every calculated column without
>>>regard or precision.
>>>And at execute time the f2 column has varying type decimals (in row 2
>>>you can see 4 decimals and in other rows has 3 decimals), this is not a
>>>behavior , this is an ERROR.
>>>      
>>>
>
>[Jumping in, because this was the first message of the thread I've seen]
>
>Technically, the correct behavior by spec would be an
>implementation-defined precision and a particular scale based on the
>argument scales. So, having numeric(6,2)+numeric(6,2) return
>numeric(65535, 2) is fine. Returning numeric(65535, 65531) isn't
>technically, but I don't think this is an issue in the jdbc metadata
>getting as much as an issue in the database proper.
>

I agree with all your spech but a  numeric data type like numeric(65535, 
2) isn't a very serious return value.
A value like this could be usefull to eliminate the need of presicion 
specification in numeric data type too.
Of course it's a dabase proper issue , but impact in my needs in jdbc 
usability.
No matter what's technically or not, a behavior at this point like those 
of db2/oracle would be very nice ;-)

view thread (11+ messages)  latest in thread

Message-ID: <40E89282.9060306@sistemat.com.ar>
Permalink:  ../40E89282.9060306@sistemat.com.ar/
Also on:    postgresql.org/message-id/40E89282.9060306@sistemat.com.ar

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: software@sistemat.com.ar, sszabo@megazone.bigpanda.com, books@ejurka.com, pgsql-jdbc@postgresql.org, pgsql-bugs@postgresql.org
  Subject: Re: [JDBC] Error in DatabaseMetaData.getColumns() with Views
  In-Reply-To: <40E89282.9060306@sistemat.com.ar>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox