We're updating the issue view to help you get more done. 

ImplicitCompositeKeyJoinTest#testImplicitCompositeJoin fails due to dialect-specific differences in generated SQL string

Description

ImplicitCompositeKeyJoinTest#testImplicitCompositeJoin fails due to dialect-specific differences in generated SQL string for Oracle, Sybase, and MySQL.

Expected SQL:

create table Employee (age varchar(15) not null, birthday varchar(255) not null, name varchar(20) not null, manager_age varchar(15), manager_birthday varchar(255), manager_name varchar(20), primary key (age, birthday, name))

oracle12c:
create table Employee (age varchar2(15 char) not null, birthday varchar2(255 char) not null, name varchar2(20 char) not null, manager_age varchar2(15 char), manager_birthday varchar2(255 char), manager_name varchar2(20 char), primary key (age, birthday, name))

sybase 15.7
create table Employee (age varchar(15) not null, birthday varchar(255) not null, name varchar(20) not null, manager_age varchar(15) null, manager_birthday varchar(255) null, manager_name varchar(20) null, primary key (age, birthday, name)) lock datarows

mysql 5.7
create table Employee (age varchar(15) not null, birthday varchar(255) not null, name varchar(20) not null, manager_age varchar(15), manager_birthday varchar(255), manager_name varchar(20), primary key (age, birthday, name)) ENGINE=InnoDB

Environment

None

Status

Assignee

Andrea Boriero

Reporter

Gail Badner

Labels

None

Worked in

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Community Help Wanted

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Affects versions

5.0.4

Priority

Major