From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | "Jaroslaw J(dot) Pyszny" <arghil(at)poczta(dot)onet(dot)pl> |
Cc: | Kris Jurka <books(at)ejurka(dot)com>, pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Auto-increment serial (Postgresql JDBC driver w/ |
Date: | 2004-09-21 22:50:31 |
Message-ID: | 1095807031.1556.129.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Sorry, missed one more where clause.
select column_default from information_schema.columns where table_name =
'xyz' and column_name = 'id';
This assumes a table defined like create table xyz (id serial);
Dave
On Tue, 2004-09-21 at 16:31, Dave Cramer wrote:
> This is probably a much more portable way to get the same information.
>
> select column_default from information_schema.columns where table_name
> = 'xyz';
>
> Dave
> On Tue, 2004-09-21 at 15:25, Jaroslaw J. Pyszny wrote:
> > W liście z wto, 21-09-2004, godz. 03:50, Kris Jurka pisze:
> > > On Mon, 21 Sep 2004, Jaroslaw J. Pyszny wrote:
> > >
> >
> > > The basic idea looks good to me, but you've made a mistake in the
> > > isAutoIncrement() method. You are using the column number from the
> > > ResultSet to look up the default when you need to actually use that
> > > column's position in the table. In fact it looks like the whole method
> > > body should be moved into the Field class much like the isNullable method
> > > does. This also avoid the contrived hash key value.
> > >
> > > Finally we prefer patches in context diff format (diff -c).
> > Thanks :)
> > I'll try fix it.
> >
> > Jarek
--
Dave Cramer
519 939 0336
ICQ # 14675561
www.postgresintl.com
From | Date | Subject | |
---|---|---|---|
Next Message | Qi, Xlaoyan | 2004-09-22 12:35:13 | Remote access with JDBC |
Previous Message | Dave Cramer | 2004-09-21 20:31:15 | Re: Auto-increment serial (Postgresql JDBC driver w/ |