Steve Holdoway tickled the keyboard with > ... what's the betting that developers are massively in favour of them??? >
There is an ANSI/ISO standard for SQL stored procedures called SQL/PSM (Persistent Stored Modules) which was standardised in 1996. However, only DB2 and the new MySQL 5 beta support it, largely because they added stored procedures and triggers to their products quite late relative to the other vendors. Everyone else does there own thing, as a result unless you make a very big commitment to one database a lot of developers avoid them and write a middle layer between the app and the database. Currently I am trying to port an interbase-v5 app to informix and oracle 7. It has been a handful trying to get as much code to be common across the three then the rest in to the middle layer. The store procedures can also be used to hide differences between database as well, but as a lot stored procedures are compiled code running in the database it is possible to bring the whole thing crashing down around your ears. Not a good look a 24x7 manufacturing environment. Maurice > -----Original Message----- > From: Steve Holdoway [mailto:[EMAIL PROTECTED] > Sent: Thursday, 18 August 2005 7:17 p.m. > To: linux-users@it.canterbury.ac.nz > Subject: Re: Database choice? > > > Timothy Pick wrote: > > >>- stored procedure support. Stored procedures are little programs that > >> can be run as database queries that can be useful for > >> standardising writes and complicated reads. > >> > >> > >Not to start a war but there is a school of thought that stored procs > >suck. Google for it and you'll find a host of debates on the issue... > > > > > ... what's the betting that developers are massively in favour of them??? > >
