Robert Haas writes:
> On Thu, Sep 17, 2009 at 10:44 AM, Andre Rothe wrote:
>> The problem is, that I get the default values from a metadata query
>> with JDBC,
>> so I have to parse every return value for such an annotation before I
>> can use them.
> That sounds annoying, but it's not a Postgre
On Thu, Sep 17, 2009 at 10:44 AM, Andre Rothe wrote:
> The problem is, that I get the default values from a metadata query
> with JDBC,
> so I have to parse every return value for such an annotation before I
> can
> use them.
That sounds annoying, but it's not a PostgreSQL bug.
> So it seems tha
The problem is, that I get the default values from a metadata query
with JDBC,
so I have to parse every return value for such an annotation before I
can
use them.
So it seems that I could change the jdbc driver to a newer version. I
use the
PostgreSQL 8.1 JDBC3 with SSL (build 407).
Thanks
Andre
On Thu, Sep 17, 2009 at 8:15 AM, Andre Rothe wrote:
> Hi,
>
> I have installed Postgres 8.3.8 on Fedora Linux. If I create a table,
> the default values will be set by the database to
>
> NULL::timestamp without time zone
>
> for a timezone column and to
>
> NULL::character varying
>
> for a varch
Hi,
I have installed Postgres 8.3.8 on Fedora Linux. If I create a table,
the default values will be set by the database to
NULL::timestamp without time zone
for a timezone column and to
NULL::character varying
for a varchar column. How I can prevent such a behaviour? Both column
defaults shou
