Last night I did a full functional test using an Oracle based dOOdad. I tested the 5 stored procs. It was a little disappointing to find that Oracle stored procedures names have a maximum length of 30 characters. The stored procedure names are as follows and truncated at 30 characters if they run over in name.
1) PK_<TableName> = LoadByPrimaryKey
2) PL_<TableName> = LoadAll
3) PU_<TableName> = Update
4) PI_<TableName> = Insert
5) PD_<TableName> = Delete
And most of the dynamic query capabilities.
Also, sequenced fields are supported through user meta data. Here's how to declare a sequenced field in the user meta data. Suppose your table is called MIKES_TABLE and it's in the HR schema. You define the user meta data for sequenced fields on the table, so, on the \"MIKES_TABLE\" table I would add this in the user meta data to hookup a sequence to a column.
Where \"THEKEY\" is a column in the MIKES_TABLE table and I want it's value during an INSERT to be derived from the EMPLOYEES_SEQ Oracle Sequence. Notice also that the \"p_THEKEY
\" parameter is marked OUT
and available in your dOOdad immediately after save.
- Code: Select all
CREATE OR REPLACE PROCEDURE \"HR\".\"PI_MIKES_TABLE\"
p_FIRST_NAME IN MIKES_TABLE.FIRST_NAME%type,
p_LAST_NAME IN MIKES_TABLE.LAST_NAME%type,
p_THEKEY OUT MIKES_TABLE.THEKEY%type
SELECT HR.EMPLOYEES_SEQ.NextVal INTO p_THEKEY FROM DUAL;