From: Erwin Moller Date: 2004-04-21T20:59:09+09:00 Subject: Re: The quest for opensource database... Tony Marston wrote: > > "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. >> >> 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. 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. > > 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. Have you come > across an interactive debugger for database procedures and triggers? > Very good advise, Tony. I second that opinion 100%. Been there too. :-( Stick to constrainst like foreign keys (which do fire a trigger I think when the relevant colums are updated/inserted) and avoid writing your own. And stick to constraints like CHECK to make sure the data inserted makes sense to you instead of triggers. Stored procedures do often shorten the developmenttime, but are hard to debug. It is often easy to do 'some quick and dirty' solution using stored procedures, but when something changes in the application (which happens all the time) you have to debug those SP's too. Regards, Erwin Moller