We want to use temporary procedures in database procedures but when we do, the source column of the procedure's entry in the sysprocedure table is set to null. That makes it hard to edit the procedure using Sybase Central or other tools.
We are currently using SQL Anywhere version 220.127.116.118.
Here is an example of a simple procedure that cause the issue :
Is this a known issue or is there something we are missing to make this work as expected?
asked 01 Mar '16, 14:34
Short answer: Yes this is known behaviour and is the expected behaviour.
A temporary procedure only exists on the connection that created it and never gets added to the catalog, and as such there is no change made to the database. I.e. there is no permanent procedure source that needs to be added to the database catalog because the procedure is not permanent.
answered 01 Mar '16, 14:53