| From: | Giuseppe Sacco <giuseppe(at)eppesuigoccas(dot)homedns(dot)org> |
|---|---|
| To: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: DDL in transactions? |
| Date: | 2005-03-31 17:24:03 |
| Message-ID: | 424C3233.9070109@eppesuigoccas.homedns.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Kris Jurka wrote:
[...]
>>My question is: why? Shouldn't DDL be executed immediately?
>
>
> No. DDL in postgresql is fully transactable and may be rolled back or
> committed. That doesn't explain why the above code doesn't work.
> Because the two executeUpdates are on the same Statement on the same
> Connection the second execution should see the newly created table because
> it is in the same transaction. Perhaps you are not showing us the real
> code you are using and you actually have two connections?
Thanks Kris, I am going to check it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schaber | 2005-03-31 17:34:14 | Re: DDL in transactions? |
| Previous Message | Kris Jurka | 2005-03-31 16:09:34 | Re: DDL in transactions? |