Status: Open (View Workflow)
CentOS 7, RHEL 7, MariaDB 10.3
The following conditions should be handled by setting SQL_MODE to ORACLE:
- CHAR and VARCHAR column definition can be written as "...CHAR( 20 BYTE )". In reading Oracle's SQL Reference it is not clear if the intended behavior should honor multi-byte character sets. Ours does not understand, if even to just ignore it, the "BYTE" keyword.
CREATE TABLE may be closed with the following parameters:
- Each of these has a positive counterpart, LOGGING, COMPRESS, PARALLEL to enable these features explicitly. It appears the SQLDeveloper tools explicitly disable them in DDL exports regardless of the default values. This prompted this bug to be filed as it relates to migration projects.
I do not see feature parity in MariaDB 10.3 except for COMPRESS. We could translate this to " ROW_FORMAT=COMPRESSED". At a minimum we should ignore these key words under the ORACLE sql_mode.
- CREATE VIEW ( ... ) WITH READ ONLY; in Oracle defines the view as read-only. It does not seem like we have an explicit control for this when defining views.