-
Notifications
You must be signed in to change notification settings - Fork 4
feat(plsql): fill CREATE TABLE grammar gaps against Oracle 19c spec #66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,127 @@ | ||
| -- Regression fixtures for CREATE TABLE grammar gaps closed against Oracle 19c docs. | ||
| -- Each block below previously failed to parse; see PR description for details. | ||
|
|
||
| -------------------------------------------------------------------------------- | ||
| -- Tier 1: partition value clauses accept full expressions (fixes BYT-9302) | ||
| -------------------------------------------------------------------------------- | ||
|
|
||
| -- DATE typed literal in RANGE bound with INTERVAL partitioning | ||
| CREATE TABLE gcp.lead_drop_mc_native_data ( | ||
| txn_date DATE, | ||
| userid VARCHAR2(100), | ||
| custid VARCHAR2(100), | ||
| screenid VARCHAR2(500), | ||
| eventtime DATE, | ||
| status NUMBER | ||
| ) | ||
| PARTITION BY RANGE (txn_date) | ||
| INTERVAL (NUMTODSINTERVAL(1,'DAY')) | ||
| (PARTITION p0 VALUES LESS THAN (DATE '2026-01-01')); | ||
|
|
||
| -- TIMESTAMP typed literal in RANGE bound | ||
| CREATE TABLE range_ts (d TIMESTAMP) | ||
| PARTITION BY RANGE (d) | ||
| (PARTITION p0 VALUES LESS THAN (TIMESTAMP '2026-01-01 00:00:00')); | ||
|
|
||
| -- Arithmetic expression in RANGE bound | ||
| CREATE TABLE range_expr (c NUMBER) | ||
| PARTITION BY RANGE (c) | ||
| (PARTITION p0 VALUES LESS THAN (10*10 + 5)); | ||
|
|
||
| -- NULL in LIST values | ||
| CREATE TABLE list_null (c VARCHAR2(10)) | ||
| PARTITION BY LIST (c) | ||
| (PARTITION p0 VALUES (NULL, 'a', 'b')); | ||
|
|
||
| -- Expression in LIST values | ||
| CREATE TABLE list_expr (c NUMBER) | ||
| PARTITION BY LIST (c) | ||
| (PARTITION p0 VALUES (1+2, 3*3)); | ||
|
|
||
| -- Multi-column LIST partitioning with tuple form | ||
| CREATE TABLE list_multi_col (a NUMBER, b NUMBER) | ||
| PARTITION BY LIST (a, b) | ||
| ( | ||
| PARTITION p0 VALUES ((1,2),(3,4)), | ||
| PARTITION p1 VALUES ((5,6)) | ||
| ); | ||
|
|
||
| -------------------------------------------------------------------------------- | ||
| -- Tier 2: IF NOT EXISTS, LIST AUTOMATIC, blockchain flexibility | ||
| -------------------------------------------------------------------------------- | ||
|
|
||
| -- IF NOT EXISTS on CREATE TABLE | ||
| CREATE TABLE IF NOT EXISTS t_ine (a NUMBER, b VARCHAR2(10)); | ||
|
|
||
| -- AUTOMATIC list partitioning | ||
| CREATE TABLE list_auto (c NUMBER) | ||
| PARTITION BY LIST (c) AUTOMATIC | ||
| (PARTITION p0 VALUES (1)); | ||
|
|
||
| -- Blockchain: new DAYS IDLE form on retention clause, with single-quoted algorithm/version | ||
| CREATE BLOCKCHAIN TABLE bc_idle (a NUMBER) | ||
| NO DROP UNTIL 0 DAYS IDLE | ||
| NO DELETE UNTIL 16 DAYS IDLE | ||
| HASHING USING 'SHA2_512' VERSION 'v1'; | ||
|
|
||
| -- Blockchain: drop/retention clauses both omitted (only the hash clause is required) | ||
| CREATE BLOCKCHAIN TABLE bc_hash_only (a NUMBER) | ||
| HASHING USING "SHA2_512" VERSION "v1"; | ||
|
|
||
| -------------------------------------------------------------------------------- | ||
| -- Tier 3: CONSISTENT HASH and PARTITIONSET | ||
| -------------------------------------------------------------------------------- | ||
|
|
||
| -- Consistent hash partitioning | ||
| CREATE TABLE ch_simple (a NUMBER) | ||
| PARTITION BY CONSISTENT HASH (a) | ||
| PARTITIONS AUTO; | ||
|
|
||
| -- Consistent hash with range sub-partitioning | ||
| CREATE TABLE ch_sub (a NUMBER, d DATE) | ||
| PARTITION BY CONSISTENT HASH (a) | ||
| PARTITIONS AUTO | ||
| SUBPARTITION BY RANGE (d) | ||
| SUBPARTITIONS AUTO; | ||
|
|
||
| -- Range partitionset | ||
| CREATE TABLE range_ps (a NUMBER, b NUMBER) | ||
| PARTITION BY PARTITIONSET RANGE (a) | ||
| ( | ||
| PARTITIONSET ps1 VALUES LESS THAN (100) | ||
| (PARTITION p1 VALUES LESS THAN (10)) | ||
| ); | ||
|
|
||
| -- List partitionset | ||
| CREATE TABLE list_ps (a NUMBER, b NUMBER) | ||
| PARTITION BY PARTITIONSET LIST (a) | ||
| ( | ||
| PARTITIONSET ps1 VALUES (1,2,3) | ||
| (PARTITION p1 VALUES (1)) | ||
| ); | ||
|
|
||
| -------------------------------------------------------------------------------- | ||
| -- Tier 4: subpartition read_only / indexing clauses + column annotations | ||
| -------------------------------------------------------------------------------- | ||
|
|
||
| -- read_only_clause on range_subpartition_desc (inside composite range partitioning) | ||
| CREATE TABLE comp_range_ro (a NUMBER, d DATE) | ||
| PARTITION BY RANGE (d) | ||
| SUBPARTITION BY RANGE (a) | ||
| (PARTITION p0 VALUES LESS THAN (DATE '2026-01-01') | ||
| (SUBPARTITION sp0 VALUES LESS THAN (100) READ ONLY, | ||
| SUBPARTITION sp1 VALUES LESS THAN (MAXVALUE) READ WRITE INDEXING OFF)); | ||
|
|
||
| -- indexing_clause on individual_hash_subparts | ||
| CREATE TABLE comp_hash_idx (a NUMBER, b NUMBER) | ||
| PARTITION BY RANGE (a) | ||
| SUBPARTITION BY HASH (b) | ||
| (PARTITION p0 VALUES LESS THAN (100) | ||
| (SUBPARTITION sp0 INDEXING ON, | ||
| SUBPARTITION sp1 INDEXING OFF)); | ||
|
|
||
| -- annotations_clause on column definition (Oracle 23c) | ||
| CREATE TABLE annotated_cols ( | ||
| id NUMBER ANNOTATIONS (Display 'Identifier'), | ||
| name VARCHAR2(100) ANNOTATIONS (ADD Display 'Name', MaxLength '100') | ||
| ); |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.