fix!: EXPOSED-278 Invalid Oracle statement when adding a new column that is used in a primary key

[joc-a]

Description

• What:
  DDL for column in Oracle has changed when it is part of a primary key constraint.
• Why:
  When adding a new column to an existing table in Oracle, if that new column is used in a primary key, then a separate statement is needed for the primary key otherwise there will be a syntax error. Previously, adding the column and the constraint was being done in one statement.
• How:
  In createStatement() in Column, a check was added for Oracle to include a separate statement when there is a primary constraint to be added.

---

Type of Change

Please mark the relevant options with an "X":

• Bug fix
• New feature
• Documentation update

Updates/remove existing public API methods:

• Is breaking change

Affected databases:

• MariaDB
• Mysql5
• Mysql8
• Oracle
• Postgres
• SqlServer
• H2
• SQLite

Checklist

• Unit tests are in place
• The build is green (including the Detekt check)
• All public methods affected by my PR has up to date API docs
• Documentation for my change is up to date

---

Related Issues

[bog-walk]

Please add a note about breaking changes to doc so it's not forgotten later. All links to breaking changes goes to the site version, which won't be synced until the release, so it's ok to update with every relevant PR.