On Thu, August 18, 2005 7:32 pm, Maurice Butler said: > 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. IMO the commitment to one database is done by the system architects *before* any design is completed, let alone before developers start work. It's just a s fundamental a part as the choice of programming language. That way, developers specialise in their own field, and are far more productive. > > 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. There are plenty of database neutral middleware packages/api's available already. Wouldn't it be better to port to that ( and, yes I agree that adding intelligence to the database would *not* be a good idea if you're forced down that route ). > > 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. Well, I know that oracle has it's own definition of 'compiled' in this case... and postgres is interpreted (: But adequate resting should cover the rest. > > Maurice > > Oracle 7 has been dead for YEARS! Why on earth bother porting to it. I'd go no further back than 8.1.7.4 as an absolute, and preferably 9 or 10, and I'd look to support those others pushing to open source that mere mortals *can* afford - like Ingres ( yes, I know that CA are asset strippers of the first degree, but it was the firt RDBMS I ever used ), but I would look to an api that does most of the work for you - like the PHP/Pear DB abstraction layer, which supports ( from the web page ) fbsql, ibase, informix, msql, mssql, mysql, mysqli, oci8, odbc, pgsql, sqlite and sybase.
$0.02, Steve -- Windows: Where do you want to go today? MacOS: Where do you want to be tomorrow? Linux: Are you coming or what?
