Or in this case posted on the OTN Forums, is it even desirable. It's nice to see there is the ability for the database to simply say, "I'm sorry but this code is too stupid to run".
Yes but wouldn't this just throw your average syntax related error. If they could ever compile anything on that database, then it killed the compiler, or drove it to suicide.
Reminds me of an error I saw posted once, "Oracle process has no reason for life." or something.
Thanks for removing the handbag comment btw, glad it is possible. What is it with DBAs and their handbags?
Well it could mean "I'm sorry but this code is too stupid to run" but it also seems to mean the SQLPLUS compiler is a POS at handling simple syntax errors. I've seen better syntax checking from the first compiler CompSci undergraduates write
5 comments:
I'm surprised this code didn't produce the same error.
Yes but wouldn't this just throw your average syntax related error. If they could ever compile anything on that database, then it killed the compiler, or drove it to suicide.
Reminds me of an error I saw posted once, "Oracle process has no reason for life." or something.
Thanks for removing the handbag comment btw, glad it is possible. What is it with DBAs and their handbags?
Well it could mean "I'm sorry but this code is too stupid to run" but it also seems to mean the SQLPLUS compiler is a POS at handling simple syntax errors. I've seen better syntax checking from the first compiler CompSci undergraduates write
Maybe, but this was a PL/SQL error.
Could you tell I'd just spent 30 mins trying to find a missing comma?
Post a Comment