| From: | Greg Speegle <Greg(at)10happythings(dot)com> |
|---|---|
| To: | Peter Mount <petermount(at)maidstone(dot)gov(dot)uk> |
| Cc: | pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: JDBC Drop/Create problem? |
| Date: | 2000-12-07 18:19:12 |
| Message-ID: | 3A2FD4A0.7030000@10happythings.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
Ah. That explains it. Thanks.
Out of curiosity, why does the transaction get marked as aborted? I
only ask since others
(e.g. Oracle) don't have this behavior.
Greg
Peter Mount wrote:
> Dropping a non-existent table should throw an exception as well as mark any
> open transaction as aborted.
>
> I'd say either:
>
> * using autoCommit while checking for existing tables.
> * commit and begin a new transaction afterwards.
> * Use temporary tables, so the table doesn't survive the connection.
>
> Peter
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2000-12-07 19:48:25 | v7.1 beta 1 ...packaged, finally ... |
| Previous Message | Peter Mount | 2000-12-07 16:51:31 | RE: JDBC Drop/Create problem? |