From: | Mofeed Shahin <mofeed(dot)shahin(at)dsto(dot)defence(dot)gov(dot)au> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Multi column foreign keys. |
Date: | 2003-12-10 22:31:00 |
Message-ID: | 200312110901.00049.mofeed.shahin@dsto.defence.gov.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Wed, 10 Dec 2003 01:31 pm, you wrote:
> On Wed, 10 Dec 2003, Mofeed Shahin wrote:
> > Some questions though:
> > When I do
> > DatabaseMetaData metaData = connection.getMetaData ();
> > ResultSet tableResultSet = metaData.getTables ("", null, null, new
> > String[]{"TABLE"})
> >
> > I'm actually getting alot more tables than I wanted. I seem to be getting
> > all the system tables, which I don't want.
>
> With 7.4 came the information_schema which I believe is what you are
> seeing. The attached patch should fix that.
Once again, thanks alot. That worked very well.
Will these patches be applied to the standard jdbc driver ?
> > I also get messages like :
> > "Column is_insertable_into in table views has unknown type code 1111"
>
> This message is probably from your own code after doing
> DatabaseMetaData.getColumns() on information_schema.views. The DATA_TYPE
> column is returning java.sql.Types.OTHER which you don't know how to
> handle. Perhaps we need to look at how domains are handled here and it
> should return the base type's code, but as this problem is in the
> information schema you shouldn't have to deal with in.
Right you are. Thanks.
Mof.
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2003-12-11 01:47:13 | Re: Multi column foreign keys. |
Previous Message | marcelospbr | 2003-12-10 15:15:16 | JDBC function call (getting resultset) |