Skip to Main Content
Forums

SQL & PL/SQL

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Column name contains # error in trigger, but normal in stored procedure

ShenkNov 13 2019 — edited Nov 13 2019

Hello everyone.

This is a problem that occurs when importing 9i data to the next 12c. For example, there is a field CC#DD in the A table. In the stored procedure, A.CC#DD can be compiled and run. In the case of OLD.CC#DD or NEW.CC#DD in the trigger, there will be compilation errors for invalid characters and bad bind variable , and the double quotes will be written as "CC#DD" and will no longer be an error.

Questions are as follows:

1. Why does the stored procedure not report an error, and the trigger will report an error?

2. The 9i trigger does not use CC#DD with double quotes. Why is there no error?

Thanks

Comments

Processing

Post Details

Added on Nov 13 2019
#procedure, #trigger
16 comments
580 views