 | |
using "call" for packaged procedure?
comp.databases.oracle.misc comp.databases.oracle.misc
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
using "call" for packaged procedure? -
08-28-2008
, 02:00 PM
#2
| |||
| |||
|
|
After moving a procedure into a package I discovered I can no longer use "call" to invoke the procedure. Can someone explain why this is? Many TIA! old code: call p4_add(:typeid,:reposid,:depotFile,:rev,:tmstamp) new code (broken): call p4.add(:typeid,:reposid,:depotFile,:rev,:tmstamp) ORA-01747: invalid user.table.column,table.column, or column specification new code (works): begin p4asset.add(:typename,:repos,:depotFile,:rev); end |
Because if not, then the solution would be obvious:
CALL p4asset.add(:typename,:repos,:depotFile,:rev);
Yours,
Laurenz Albe
#3
| |||
| |||
|
|
After moving a procedure into a package I discovered I can no longer use "call" to invoke the procedure. Can someone explain why this is? Many TIA! old code: call p4_add(:typeid,:reposid,:depotFile,:rev,:tmstamp) new code (broken): call p4.add(:typeid,:reposid,:depotFile,:rev,:tmstamp) ORA-01747: invalid user.table.column,table.column, or column specification new code (works): begin p4asset.add(:typename,:repos,:depotFile,:rev); end |
Because if not, then the solution would be obvious:
CALL p4asset.add(:typename,:repos,:depotFile,:rev);
Yours,
Laurenz Albe
#4
| |||
| |||
|
|
After moving a procedure into a package I discovered I can no longer use "call" to invoke the procedure. Can someone explain why this is? Many TIA! old code: call p4_add(:typeid,:reposid,:depotFile,:rev,:tmstamp) new code (broken): call p4.add(:typeid,:reposid,:depotFile,:rev,:tmstamp) ORA-01747: invalid user.table.column,table.column, or column specification new code (works): begin p4asset.add(:typename,:repos,:depotFile,:rev); end |
Because if not, then the solution would be obvious:
CALL p4asset.add(:typename,:repos,:depotFile,:rev);
Yours,
Laurenz Albe
#5
| |||
| |||
|
|
After moving a procedure into a package I discovered I can no longer use "call" to invoke the procedure. Can someone explain why this is? Many TIA! old code: call p4_add(:typeid,:reposid,:depotFile,:rev,:tmstamp) new code (broken): call p4.add(:typeid,:reposid,:depotFile,:rev,:tmstamp) ORA-01747: invalid user.table.column,table.column, or column specification new code (works): begin p4asset.add(:typename,:repos,:depotFile,:rev); end |
Because if not, then the solution would be obvious:
CALL p4asset.add(:typename,:repos,:depotFile,:rev);
Yours,
Laurenz Albe
#6
| |||
| |||
|
|
m... (AT) pixar (DOT) com wrote: After *moving a procedure into a package I discovered I can no longer use "call" to invoke the procedure. Can someone explain why this is? Many TIA! old code: * *call p4_add(:typeid,:reposid,:depotFile,:rev,:tmstamp) new code (broken): * *call p4.add(:typeid,:reposid,:depotFile,:rev,:tmstamp) * *ORA-01747: invalid user.table.column,table.column, * * * * * * * or column specification new code (works): * *begin p4asset.add(:typename,:repos,:depotFile,:rev); end Are there typos in your posting? Because if not, then the solution would be obvious: CALL p4asset.add(:typename,:repos,:depotFile,:rev); Yours, Laurenz Albe- Hide quoted text - - Show quoted text - |
is pointing out that your spelled the package name different in your
example of what failed and what worked. Based on this the error
message was telling you the truth. Be there, done that. LOL.
It is time for the weekend!
HTH -- Mark D Powell --
#7
| |||
| |||
|
|
m... (AT) pixar (DOT) com wrote: After *moving a procedure into a package I discovered I can no longer use "call" to invoke the procedure. Can someone explain why this is? Many TIA! old code: * *call p4_add(:typeid,:reposid,:depotFile,:rev,:tmstamp) new code (broken): * *call p4.add(:typeid,:reposid,:depotFile,:rev,:tmstamp) * *ORA-01747: invalid user.table.column,table.column, * * * * * * * or column specification new code (works): * *begin p4asset.add(:typename,:repos,:depotFile,:rev); end Are there typos in your posting? Because if not, then the solution would be obvious: CALL p4asset.add(:typename,:repos,:depotFile,:rev); Yours, Laurenz Albe- Hide quoted text - - Show quoted text - |
is pointing out that your spelled the package name different in your
example of what failed and what worked. Based on this the error
message was telling you the truth. Be there, done that. LOL.
It is time for the weekend!
HTH -- Mark D Powell --
#8
| |||
| |||
|
|
m... (AT) pixar (DOT) com wrote: After *moving a procedure into a package I discovered I can no longer use "call" to invoke the procedure. Can someone explain why this is? Many TIA! old code: * *call p4_add(:typeid,:reposid,:depotFile,:rev,:tmstamp) new code (broken): * *call p4.add(:typeid,:reposid,:depotFile,:rev,:tmstamp) * *ORA-01747: invalid user.table.column,table.column, * * * * * * * or column specification new code (works): * *begin p4asset.add(:typename,:repos,:depotFile,:rev); end Are there typos in your posting? Because if not, then the solution would be obvious: CALL p4asset.add(:typename,:repos,:depotFile,:rev); Yours, Laurenz Albe- Hide quoted text - - Show quoted text - |
is pointing out that your spelled the package name different in your
example of what failed and what worked. Based on this the error
message was telling you the truth. Be there, done that. LOL.
It is time for the weekend!
HTH -- Mark D Powell --
#9
| |||
| |||
|
|
m... (AT) pixar (DOT) com wrote: After *moving a procedure into a package I discovered I can no longer use "call" to invoke the procedure. Can someone explain why this is? Many TIA! old code: * *call p4_add(:typeid,:reposid,:depotFile,:rev,:tmstamp) new code (broken): * *call p4.add(:typeid,:reposid,:depotFile,:rev,:tmstamp) * *ORA-01747: invalid user.table.column,table.column, * * * * * * * or column specification new code (works): * *begin p4asset.add(:typename,:repos,:depotFile,:rev); end Are there typos in your posting? Because if not, then the solution would be obvious: CALL p4asset.add(:typename,:repos,:depotFile,:rev); Yours, Laurenz Albe- Hide quoted text - - Show quoted text - |
is pointing out that your spelled the package name different in your
example of what failed and what worked. Based on this the error
message was telling you the truth. Be there, done that. LOL.
It is time for the weekend!
HTH -- Mark D Powell --
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.