Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Major |
| Complexity | Unknown |
| Component | App - General |
| Version | Future - .2 |
In create table GUI, let say I click "Create" button and get a server error. (e.g. I trying specifying NULL for serial data type). I then correct my error and click "Create" button again. I get an error message (see below).
ERROR: current transaction is aborted, commands ignored until end of transaction block
This exception is generated by
Connection.rollback()
from
CommonSchemaUtil.executeDDL().
Greenplum does not seem to support rollback a DDL in a transaction; in ADS, this flag is determined by the ConnectionSupport.supportDDLRollback() method. For Greenplum, if we let ConnectionSupport.supportDDLRollback() return TRUE and a DDL execution error occurred, then subsequent DDL/DML executions always throw this exception:
ERROR: current transaction is aborted, commands ignored until end of transaction block
I have tried incorrect CREATE/ALTER TABLE/VIEW/FUNCTION followed by other DDL and SELECT statements, all failed.
For the time being, we worked around this problem by returning FALSE from ConnectionSupport.supportDDLRollback() for Greenplum. SVN r30363.
fixed
fixed
Issue #7941 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build trunk/30363 |
| No time estimate |
2 issue links |
relates to #8105
Issue #8105For Greenplum FluidShell connection, get error that current transaction is aborted |
blocks #7919
Issue #7919Add Greenplum Support |
This exception is generated by
Connection.rollback()
from
CommonSchemaUtil.executeDDL().
Greenplum does not seem to support rollback a DDL in a transaction; in ADS, this flag is determined by the ConnectionSupport.supportDDLRollback() method. For Greenplum, if we let ConnectionSupport.supportDDLRollback() return TRUE and a DDL execution error occurred, then subsequent DDL/DML executions always throw this exception:
ERROR: current transaction is aborted, commands ignored until end of transaction block
I have tried incorrect CREATE/ALTER TABLE/VIEW/FUNCTION followed by other DDL and SELECT statements, all failed.
For the time being, we worked around this problem by returning FALSE from ConnectionSupport.supportDDLRollback() for Greenplum. SVN r30363.