All the functions from the old package are available in the new package, but due to differences in the definition of arguments, etc., it is necessary to change the calling method when executing each function. Below is an overview of the changes to each function. Note that all the names are the same.
Feature | Type in old package | Type in new package | Number of arguments | Other points to note |
---|---|---|---|---|
BIND_VARIABLE | function | procedure or | different | |
CLOSE_CURSOR | function | procedure | same | |
COLUMN_VALUE | function | procedure or | same | Be careful how you select columns |
DEFINE_COLUMN | function | procedure | same | |
EXECUTE | function | function | same | |
FETCH_ROWS | function | function | same | |
OPEN_CURSOR | function | function | different | |
PARSE | function | procedure | different |
Due to the above differences, the following actions are required when migrating from the old package. For details, please refer to the modification method for each feature.
Differences in types
If the new calling method is a procedure, the following changes will be required:
How to call in old package | How to call in new package |
---|---|
perform function name Example: perform BIND_VARIABLE | Call procedure name Example: Call BIND_VARIABLE |
Also, if you want to use a function in a feature that provides both procedures and functions, you will need to change the function name.
How to call in old package | How to call in new package |
---|---|
perform function name Example: perform BIND_VARIABLE | perform procedure name_f Example: perform BIND_VARIABLE_f |
Differences in arguments
There are optional arguments that can only be specified in the old package. If they are omitted, no action is required. If they are set, you will need to delete the argument or add alternative processing for that argument.