From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ODBC & v7.0(Rel) Errors with Users and Databases |
Date: | 2000-05-17 17:18:23 |
Message-ID: | Pine.LNX.4.21.0005162235320.362-100000@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dave Page writes:
> ERROR: DROP DATABASE: May not be called in a transaction block
This command can't be rolled back so you aren't allowed to try. This was
thought as an improvement. In general, a database isn't a database object
so one shouldn't be transacting around with them. (Same goes for users.)
> The ODBC log (and knowledge that it isn't pgAdmin or M$ ADO) shows that the
> ODBC driver is automatically wrapping the query in a transaction.
I don't know anything about ODBC but it certainly should provide a means
to execute a command without that wrapping block. Is this a special
function or do you just execute some exec("DROP DATABASE") style call?
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-05-17 17:18:46 | Re: Proposal for fixing numeric type-resolution issues |
Previous Message | Patrick Robin | 2000-05-17 17:13:20 | pg_dump return failed sanity check |