Closed c-bik closed 6 years ago
The current grammar definition does not contain any constraints (the keyword CONSTRAINT is not included in the grammar). The attached document shows the current CONSTRAINT definition in the Oracle CREATE TABLE statement. Please make a decision which parts should be included in sqlparse.
@stoch @c-bik
Below are the railroad diagrams extracted from @walter-weinmann 's PDF (comment above) for ease of reference to discussion:
This issue is just an observation on current sqlparse support / coverage, please feel free to choose / prioritize betwwen optional paths among the rules to impelment based other projects' need. The projects I am looking at has no requirement for this as of now (workarounds exists). Perhaps a cosmetic need in DDErl.
@stoch please decide!
constraint::=
inline_constraint::=
out_of_line_constraint::=
inline_ref_constraint::=
out_of_line_ref_constraint::=
referances_clause::=
constraint_state::=
using_index_clause::=
index_properties::=
index_attributes::=
exceptions_clause::=
@walter-weinmann Eventually, in a first step, we might want one way to create foreign keys and constraints as separate statements. In a second step, the convenience of having this inside the create table statement might be added. For now, these statements are not needed in IMEM. In DDerl for Oracle, the statements should work in spite of the missing parser support. If that is given, the issue can be put on hold until we have a real need.
@walter-weinmann looks neat! How does the coverage look like?