RE: pgsql/src/interfaces/jdbc/org/postgresql/jdbc1 (DatabaseMetaData.java)
От | Hiroshi Inoue |
---|---|
Тема | RE: pgsql/src/interfaces/jdbc/org/postgresql/jdbc1 (DatabaseMetaData.java) |
Дата | |
Msg-id | 000301c01d13$b1d53ce0$2801007e@tpf.co.jp обсуждение исходный текст |
Ответ на | pgsql/src/interfaces/jdbc/org/postgresql/jdbc1 (DatabaseMetaData.java) (Bruce Momjian - CVS <momjian>) |
Ответы |
Re: [HACKERS] RE: pgsql/src/interfaces/jdbc/org/postgresql/jdbc1
(DatabaseMetaData.java)
|
Список | pgsql-committers |
> -----Original Message----- > From: Behalf Of Bruce Momjian - CVS > [snip] - ----------------------------- Log Message ----------------------------- > > As if my JDBC patch hasn't already caused enough grief, there is now a > one-line change necessary. Due to the Mark Holloman "New Relkind for > Views" patch, my support for views in the driver will need to be updated > to match. The change to DatabaseMetaData.getTableTypes[][] is as > follows: > > - {"VIEW", "(relkind='r' and relhasrules='t' and relname !~ > '^pg_' and relname !~ '^xinv')"}, > + {"VIEW", "(relkind='v' and relname !~ '^pg_' and relname > !~ '^xinv')"}, > Current jdbc driver seems to be able to get no VIEW information from any RELEASE version of backends. Hmm,it seems that client app/libs don't mind backward incompatibility. Don't I have to bother about backward incomatibility which would be caused by my change ? If so,I would commit my change about ALTER TABLE DROP COLUMN. Regards. Hiroshi Inoue
В списке pgsql-committers по дате отправления: