From: gmuldoon Date: 2004-04-22T09:14:09+09:00 Subject: Re: The quest for opensource database... tony@NOSPAM.demon.co.uk says... > > "Ruby Tuesdays" wrote in message > news:c63aer$7ck4g$1@ID-205437.news.uni-berlin.de... > > Perhaps you database guru able to suggest what would be a good choice for > > opensource database platform to use to develop projects. Sorry, can't confidently recommend. Am spoilt, have Oracle. > > At the moment the project is small/medium, but it will grow in size both > > data, users, and number of transactions. I'm using MySQL for right now but > > it lack of trigger, stored procedures, etc ... it sometimes slows the > > project. > > You do not need stored procedures or database triggers to write successful > applications. But they can be very beneficial. > I once had to maintain a system that was built around > procedures and triggers, and it was a nightmare. The problem was that one > trigger/procedure updated several tables, which fired more triggers which > contained more updates which fired more triggers ..... It was impossible to > keep track of what was being fired where. Bad design/code is bad design/code no matter at what "layer" it is written. Doesn't mean you should throw the baby out with the bath water. > Another reason I prefer to put all my business logic into PHP code instead > of triggers is that PHP code is a lot easier to debug. I use stored procedures and triggers for things like serialized transactions, audit logs and complex calculations. In general (in Oracle at least) nearly everything that can be done inside the "database level" is more efficient, sometimes massively so, than the same thing written at the PHP "application level". I've fought similar anti-database-level-coding arguments against the use of database referential integrity constraints. > Have you come across > an interactive debugger for database procedures and triggers? For Oracle many exist, if you have the necessary $$$. Geoff M