Re: C in stored procedures

You wrote:

: Oracle Corp call routines in the kernel from within some of their
: packaged procedures but as yet have not allowed/supported user sites
: adding OBJ files (callable routines) to the kernel. Maybe one day
: they will let us do it, but not yet. They also have the problem that
: if they start allowing 3rd party products to reside inside the kernel
: then these 3rd party products might compete with them and cause them
: to lose profits.

I don't suppose it has anything to do with profits. 3rd party vendors in general only provide added value. The main issue is that if Oracle would let anyone link in 3GL code in the kernel, and there is a bug in this code (pointer problem or so), this could destroy your complete database, as it runs under the Oracle privilege!!! I don't think anyone would like this, and Oracle wouldn't like to support this.

An alternative approach is externalizing your 3GL (e.g. C) code in a seperate process and do some message passinf between PL/SQL and the C program with e.d. DBMS_PIPES or DBMS_ALERTS. This is what these packages are meant for. (seem Oracle7 Application Developers Guid for some example code)

Sandor Nieuwenhuijs
Oracle Netherlands Received on Fri Jun 17 1994 - 13:43:21 CEST