That's only if you access it directly from client. What I was talking about is AppServer sitting next to MySQL server. Preferably on the same computer. Agree that for some cascade actions triggers are very useful.
But most of the folks just try to push all business logic into sp/triggers. And that's better to do in AppServer for large-scale apps. So it's strange when the initial poster said that they are "core of his development". Because they shouldn't be. Yuri. Yuri. > I don't agreed Yuri. triggers and sp are really useful and make the > process > run faster. Think on this: the user is trying to delete a record on a > table. > The primary key of that table is present in several other tables in > the > database. Before deleting the record you should search in every table > for > the primary key to be deleted, and if you find it the record couldn't > be > deleted. > > > > Well, with triggers and sp, all the job of opening every related table > and > look for the primary key will take place in the server, minimizing time > and > network traffic. > > > > Without triggers and sp, you have to manually code the process and > every > table you open is a request to the server and data navigating trough > the > network. The process is slower and more vulnerable in a non secure > network. > > > > In an Internet environment triggers and sp take more importance. --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
