| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | books(at)ejurka(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: rule and JDBC |
| Date: | 2004-01-29 05:07:10 |
| Message-ID: | 20040129.140710.48531364.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > It seems JDBC driver does not handle if a INSERT SQL statement
> > performed by executeUpdate() is actually a SELECT, which is rewritten
> > by the rule system.
>
>
> The JDBC spec says an exception should be thrown if "the given SQL
> statement produces a ResultSet object" which it does. As you note using
> executeQuery works, but won't if there isn't a rule. Perhaps using plain
> execute() would be the most appropriate thing to do.
>
> Kris Jurka
Got it. With regard to this PostgreSQL JDBC driver confirms the JDBC
spec.
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | BARTKO, Zoltan | 2004-01-29 07:29:14 | msg translation into sk_SK, Docs: SGML -> XML |
| Previous Message | Kris Jurka | 2004-01-29 05:00:11 | Re: rule and JDBC |