Support crud operations

[buzzia2001]

Changes

This PR allows you to generate INSERT/DELETE/UPDATE statements for tables.

How to test this PR

From the SCHEMA BROWSER, select a a table, now you'll see "INSERT/DELETE/UPDATE" under Generate SQL menu:

Insert example:

Update example, no primary key detected:

Delete example:

@forstie @ryan-moeller21 could you test it?

Checklist

• have tested my change
• have created one or more test cases
• updated relevant documentation
• Remove any/all console.logs I added
• have added myself to the contributors' list in CONTRIBUTING.md

Closes #141

[github-actions]

👋 A new build is available for this PR based on 86752ce.

• Download here.
• Read more about how to test

[ryan-moeller21]

I'm not sure if just looking at whether or not the column is an identity column is sufficient.

For example, would this code handle the below example well? There are a few different generated columns that are not identity columns. Perhaps you also need to take into account whether the column has a default (HAS_DEFAULT column in SYSCOLUMNS).

-- If I create this table on COMMON76:
CREATE OR REPLACE TABLE RMOELLER.MYTABLE (
            C1 INT GENERATED BY DEFAULT AS IDENTITY,
            C2 TIMESTAMP GENERATED FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP NOT NULL,
            C3 TIMESTAMP(12) GENERATED AS ROW BEGIN NOT NULL,
            C3E TIMESTAMP(12) GENERATED AS ROW END NOT NULL,
            C4 TIMESTAMP(12) GENERATED AS TRANSACTION START ID NOT NULL,
            PERIOD FOR SYSTEM_TIME (C3, C3E)
        )
    ON REPLACE DELETE ROWS;

-- IS_IDENTITY is only 'YES' for column C1
SELECT COLUMN_NAME,
       IS_IDENTITY,
       HAS_DEFAULT
    FROM QSYS2.SYSCOLUMNS
    WHERE TABLE_SCHEMA = 'RMOELLER'
          AND TABLE_NAME = 'MYTABLE';
          
-- ACS generates the following:
INSERT INTO RMOELLER.MYTABLE (
  C1,   /* C1   INTEGER          */
  C2,   /* C2   TIMESTAMP        */
  C3,   /* C3   TIMESTAMP(12)    */
  C3E,  /* C3E  TIMESTAMP(12)    */
  C4    /* C4   TIMESTAMP(12)    */
)
VALUES (
  DEFAULT,  /* INTEGER        Generated Value: Identity                */
  DEFAULT,  /* TIMESTAMP      Generated Value: Row change              */
  DEFAULT,  /* TIMESTAMP(12)  Generated Value: Row begin               */
  DEFAULT,  /* TIMESTAMP(12)  Generated Value: Row end                 */
  DEFAULT  /* TIMESTAMP(12)  Generated Value: Transaction start ID    */
);

[ryan-moeller21]

You can still insert a row into the table if it contains exclusively identity columns, you just need to insert all DEFAULT values -- see my comment above. I'm not sure if we will ever encounter a situation where an insert statement cannot be generated. Do we need this error message?

[ryan-moeller21]

You check for the long and short table names - should you also be checking for the long and short schema/library name here?

[buzzia2001]

@ryan-moeller21 I've integrated the default type as implemented in ACS; as you can see, this is the output I get based on your table:

I've added a check on the schema name to support both system names and long names: