[quote=420819:@Alexis Colon Lugo]
ERROR: current transaction is aborted, commands ignored until end of transaction block[/quote]
if the transaction is already aborted, all following commands (correct or not) are ignored and you get the error mentioned. So if you are looking for the problem, you have to look to the error that happened before the mentioned one, with a query earlier in the same transaction. To recover, you can only ROLLBACK or ROLLBACK TO SAVEPOINT if such exists.
Demo:
[code]$ psql -X
psql (10.5)
Type “help” for help.
user=# begin;
BEGIN
user=# select ‘ok’;
?column?
ok
(1 row)
user=# select error;
ERROR: column “error” does not exist
LINE 1: select error;
^
user=# select ‘ok’;
ERROR: current transaction is aborted, commands ignored until end of transaction block
user=# select error;
ERROR: current transaction is aborted, commands ignored until end of transaction block
user=# rollback;
ROLLBACK
user=# begin;
BEGIN
user=# select ‘ok’;
?column?
ok
(1 row)
user=# savepoint sp;
SAVEPOINT
user=# select error;
ERROR: column “error” does not exist
LINE 1: select error;
^
user=# select ‘ok’;
ERROR: current transaction is aborted, commands ignored until end of transaction block
user=# rollback to savepoint sp;
ROLLBACK
user=# select ‘ok’;
?column?
After the DB.SQLExecute check the db.error property and if true see what the db.ErrorMessage is. It will almost always tell you exactly what the error is from the database perspective.
hola alexis… la consulta es parte de una transaccion? en caso de que si… podrias ejecutar la consulta de forma individual (no como parte de una transaccion) desde xojo e indicarme que mensaje de error aparece exactamente?
Well, the errormessage is “ERROR: current transaction is aborted, commands ignored until end of transaction block”. That’s exactly what the server returns in the scenario that Tobias showed.