Well, because the change to the parser and the VIO layer were major, and because it wasn't merged, it drifted, and it really drifted as major releases were added. At this point, with the X protocol, and changes to triggers so that you can have more than one, and various other changes, it is very hard to merge. I gave a go at it, but I'm not familiar enough with the server to do it, so I gave up. I came up with a different way to run SQL in the server, and for plugging in other languages I just use the gearman UDF which runs them out of process safely (but they can't run SQL on the THD, if they want to use a connection they have to create a new one). On Mon, Nov 7, 2016 at 4:42 PM, Sergei Golubchik <serg@mariadb.org> wrote:
Hi, Justin!
On Nov 07, Justin Swanhart wrote:
We discussed it here and it seemed vary popular. WL-820.
I know, right?
A cool and useful feature, I'd say. I cannot understand why it's constantly being pushed down for the last 10 years.
I still hope we get it someday.
On Mon, Nov 7, 2016 at 10:43 AM, Sergei Golubchik <serg@mariadb.org> wrote:
Hi, Federico!
On Nov 07, Federico Razzoli wrote:
Some good points from Bill Karwin: https://www.quora.com/What-are-the-reasons-not-to-use-or- not-use-stored-procedures/answer/Bill-Karwin
Thanks.
These are valid points, and some of them are related. For example, "does not have a rich library of functions or standard procedures" that follows from "does not support packages". Which might be fixed in https://jira.mariadb.org/browse/MDEV-10591
External languages for stored procedures - that's a very cool feature, and patches exist for many years. But, apparently, it's more cool than practically useful? There were almost no requests for it, not when I was in MySQL, not in MariaDB. And, frankly, I do not know why, this looks insanely useful to me.
Regards, Sergei Chief Architect MariaDB and security@mariadb.org