Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!apple!gateway.qm.apple.Com!Bob_Campbell.ZORRO From: Bob_Campbell.ZORRO@gateway.qm.apple.Com (Bob Campbell) Newsgroups: comp.databases Subject: Ingres DB Procedures Message-ID: <5585@internal.Apple.COM> Date: 4 Dec 89 22:51:07 GMT Sender: usenet@Apple.COM Organization: Apple Computer, Inc. Lines: 25 References:<7114@sybase.sybase.com> <6895@sybase.sybase.com> <2184@kodak.UUCP> <375@xyzzy.UUCP> <510@xyzzy.UUCP> <7185@sybase.sybase.com> <7189@sybase.sybase.com> <4167@rtech.rtech.com> Quotes from the Ingres release 6 (Dec 88) manual: "Procedure can be created or dropped in the SQL Termanal Monitor or within Embedded SQL. Procedures can only be executed from within Embedded SQL." "You cannot invoke a procedure Interactively or from inside another procedure." Since you can't execute a procedure from isql, I would assume that you can't dynamicly execute a stored procedure from embedded SQL (if you could execute it dynamicly from embedded SQL then there would be no good reason that you can't execute it from isql :-) Given the above statements you are clearly not as functional as Sybase stored procedures, or did I miss something? Sybase stored procedures can also retrieve data. The Sybase model for retrieving data does not support cursors the way that Ingres and other brands do and this allows procedures to return the results from one or more select statements. (I am not saying that I am a big fan of this implementation, but it does have a few advantages as well as disadvantages). I don't have a cute trailer************** Applelink: BOBC (BOBC@Applelink.apple.com) Quickmail: Bob Campbell@ZORRO (Bob_Campbell.ZORRO@gateway.qm.apple.com) Brought to you by Super Global Mega Corp .com