Make 2Pack transaction safe (for postgres)

Description

At this moment 2Pack executes a commit statement on certain DDL statements, like CREATE TABLE.

This was developed that way because Oracle has an implicit COMMIT on DDL statements, and we wanted to make the behavior of 2Pack consistent between oracle and postgresql.

But postgresql doesn't have that restriction, so in principle a 2pack in postgresql can be rolled back even if it contains DDL statements (not in oracle).

Proposal here is to create a SysConfig key to drive if we want the actual behavior (2PACK_COMMIT_DDL) or exploit the full postgresql power on this.

Regards,

Carlos Ruiz

Environment

None

Assignee

Carlos Ruiz

Reporter

Carlos Ruiz

Labels

None

Tested By

None

Priority

Major
Configure