From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | ODBC & v7.0(Rel) Errors with Users and Databases |
Date: | 2000-05-10 11:22:23 |
Message-ID: | 8568FC767B4AD311AC33006097BCD3D609177D@woody.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Hi,
First off, thanks to the developers for version 7!
I have a fairly major problem in the code for pgAdmin with CREATE/ALTER/DROP
USER/DATABASE. Any code that executes any of the SQL listed results in an
error along the lines of:
ERROR: DROP DATABASE: May not be called in a transaction block
The ODBC log shows that either ADO or the ODBC driver is automatically
wrapping the query in a transaction:
conn=47987408, query='BEGIN'
conn=47987408, query='DROP DATABASE "matt"'
ERROR from backend during send_query: 'ERROR: DROP DATABASE: May not be
called in a transaction block'
conn=47987408, query='COMMIT'
STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while
executing the query'
------------------------------------------------------------
hdbc=47987408, stmt=49221232, result=0
manual_result=0, prepare=0, internal=0
bindings=0, bindings_allocated=0
parameters=0, parameters_allocated=0
statement_type=6, statement='DROP DATABASE "matt"'
stmt_with_params='DROP DATABASE "matt"'
data_at_exec=-1, current_exec_param=-1, put_data=0
currTuple=-1, current_col=-1, lobj_fd=-1
maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0,
scroll_concurrency=1
cursor_name='SQL_CUR02EF0E70'
----------------QResult Info
-------------------------------
CONN ERROR: func=SC_execute, desc='', errnum=110, errmsg='ERROR: DROP
DATABASE: May not be called in a transaction block'
------------------------------------------------------------
henv=47987392, conn=47987408, status=1, num_stmts=16
sock=47980304, stmts=47980352, lobj_type=27904
---------------- Socket Info -------------------------------
socket=488, reverse=0, errornumber=0, errormsg='(NULL)'
buffer_in=47993744, buffer_out=47997848
buffer_filled_in=3, buffer_filled_out=0, buffer_read_in=2
conn=47987408, SQLDisconnect
Any thoughts/suggestions would be welcomed!!
Regards,
Dave.
--
"I find an axe is the most satisfying, but really any good weapon will do."
- Sacha Roscoe, explaining basic systems administration.
http://www.vale-housing.co.uk/ (Work)
http://www.pgadmin.freeserve.co.uk/ (Home of pgAdmin)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-05-10 13:52:48 | Re: ECPG failed and Postmaster getting bigger in using perl Pg |
Previous Message | SAKAIDA Masaaki | 2000-05-10 10:53:28 | Re: ECPG failed and Postmaster getting bigger in using perl Pg |