On Tue, 20 Apr 2004 09:25:58 -0500, Peter Brawley wrote: >>If you are going to have a database that will be centralized for the > company >>and will have many different clients accessing it, I would tell them not to > use >>MySQL. > > OK, though 5.0 makes it possible to write stored procs that protect clients > from MySQL's gotchas, and that keep database-protecting validation where it > belongs--on the server. > > PB
I can't speak on 5.0 since I'm not using it. If 5.0 allows the database-protecting validation on the server then my main gripe with it would be null and void and then I could recommend it for the situations I mentioned. But not any of the current versions. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Stormblade (Shaolin Code Warrior) Software Developer (15+ Years Programming exp.) My System: http://www.anandtech.com/mysystemrig.html?rigid=1683 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
