From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | the6campbells <the6campbells(at)gmail(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: data type of projected item in a union not correct |
Date: | 2012-09-25 03:31:20 |
Message-ID: | alpine.BSO.2.00.1209242317380.1873@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Mon, 24 Sep 2012, the6campbells wrote:
> The following projection is not described with the expected type+precision
> as one would expect from ISO-SQL
>
> Is this a known Postgres bug, quirk or ....
This is a serverside problem. Try the same test in psql or similar.
jurka=# create table t as select 'a'::varchar(32) as c1,
'b'::varchar(32) as c2 union select 'c'::char(32),
'd'::varchar(32);
SELECT 2
jurka=# \d t
Table "public.t"
Column | Type | Modifiers
--------+-----------------------+-----------
c1 | character varying |
c2 | character varying(32) |
As you can see the c1 column has had the length information dropped.
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | GEISINGER Marc - Contractor | 2012-09-26 14:38:23 | Re: Bug in AbstracJdbc2Statement.replaceProcessing when using dollar quoting? |
Previous Message | Kris Jurka | 2012-09-25 03:17:27 | Re: Bug in AbstracJdbc2Statement.replaceProcessing when using dollar quoting? |