More control over package names about table-api-generator HOT 4 CLOSED

Hi Jacek,

as you mentioned before - with good default values for new parameters I see no reason to not to have this parameterized. could be the same like with our p_sequence_name parameter, which also do a replacement for the given string:

Suggested parameter name: p_api_name varchar2 default null

Best regards
Ottmar

from table-api-generator.

Hi Jacek,

Additional idea: the current string replacements are driven by our existing internal table and column name short names. I could think of to grab the number inside with an regex and you as a user are free to set any number you like as long as you use #TABLE_NAME_XX# or #PK_COLUMN_XX#.

As an example: you could use then #TABLE_NAME_17#.

The #COLUMN_PREFIX# is derived automatically - in the example below the it would be EMP. If not all columns have the same prefix then it would be null.

CREATE TABLE "HR"."EMPLOYEES" (
    "EMP_ID"               NUMBER(6,0),
    "EMP_FIRST_NAME"       VARCHAR2(20 BYTE),
    "EMP_LAST_NAME"        VARCHAR2(25 BYTE),
    "EMP_EMAIL"            VARCHAR2(25 BYTE),
    "EMP_PHONE_NUMBER"     VARCHAR2(20 BYTE),
    "EMP_HIRE_DATE"        DATE,
    "EMP_JOB_ID"           VARCHAR2(10 BYTE),
    "EMP_SALARY"           NUMBER(8,2),
    "EMP_COMMISSION_PCT"   NUMBER(2,2),
    "EMP_MANAGER_ID"       NUMBER(6,0),
    "EMP_DEPARTMENT_ID"    NUMBER(4,0)
);

Best regards
Ottmar

from table-api-generator.

I forgot to tell you why we do this at all:

We need this for the SQL Developer integration - there you can select multiple tables and generate all API code at ones - so we need a way to define a variable sequence name for each selected table.

Regards
Ottmar

from table-api-generator.

Hi Jacek,

the new version 0.5.0 is out (it took a long time). You can define in this version a custom API name - therefore I close now this issue.

Best regards
Ottmar

from table-api-generator.