Re: stored procedures and triggers
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
Re: stored procedures and triggers
I would like to see the triggers/stored procedures/views in MySQL also. And the only estimate I saw somewhere was around version 5.0. But think about this this way: in the complex enterprise-level system you would probably need some kind of application server instead of direct client-db access. And if this is the case the need of triggers/sp is not that urgent. 3-teer system w/app server is actually the best scalable architecture. So you can do stuff that triggers/sp do in the app server where this stuff really belong. Lots of client-server projects convinced me that this approach is the best on the long run although somewhat more laborious. Yuri. Hello list, Here in my company people are concerned about which database to choose to start implementing a new application client-server. As the only person here with large experience in this field of activity is me, I am not very much inclined to our mysql due to its lack of resources like triggers and stored procedures, which are the kernel of my development. I would like to know from you if someone is in touch with the develolpment of these resources and know something about when they will be ready. And as second question I would like to know if some of you have had experience with interbase/firebird and know if it will always be a free database as well. hope you from the list are all well and healthy, yf marcello miorelli - 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
Re: InnoDB on FreeBSD-Alpha problem
Heikki, if you can compile with the gcc -g option and run mysqld inside gdb, then you probably see in what function and line it crashes. That's what I am going to do. If you just take a connection to mysqld, it does not execute InnoDB code at all. Well I was connecting to it before ok, but it was w/out InnoDB and older version. Yesterday I upgraded it to new stable and added InnoDB all at once. So I am not really sure it the bug was introduced with the new stable version or InnoDB enabling. Sounds more reasonable that it's just in the new stable version vs. InnoDB since it's in connect time. .So the bug is probably in the network code of MySQL or the libraries involved, for example, glibc. I guess that libraries are always involved in network communication. The kernel API is more primitive. In FreeBSD it's no glibc. And system libs aren't involved in networking. Kernel exposes POSIX-networking interface directly. So bug is somewhere in MySQL code. Will find out and make the patch. Regards, Yuri. - 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
