News for hackers. Stuff that matters.

A comment on Are triggers really that slow in Postgres?. Parent comment

Re:Are triggers really that slow in Postgres? by kbenson on Wednesday May 23, 2018 @01:53AM (#17131714)
> and a new programming language to the stack.

This was actually one of the interesting directions Drizzle SQL was exploring back in the day. It was a fork of MySQL that focused on removing old cruft, including lots of older platform support, modernizing the source, and adding modularity in a lot more places, including the use of different languages for SQL programming. Other languages like Perl, Python, Ruby, etc.

[ Parent | on HN ]
Re:Are triggers really that slow in Postgres? by krylon on Wednesday May 23, 2018 @02:50AM (#17131876)
Microsoft SQL Server allows one to write server-side code (triggers, sprocs, functions) in any language that compiles to .Net IL. There are some serious restrictions, though, as most of the .Net Framework becomes unavailable[1]. More recent version also provide for server-side R, but our SQL Server is 2014, so I have not had the option to play with that (plus, I don't know R).

[1] I was looking into writing a stored procedure for use with the Service Broker in C#, but the fact that most of the .Net Framework is unavailable (not to speak of third-party libraries) quickly put an end to my investigation.

[ Parent | on HN ]
Re:Are triggers really that slow in Postgres? by hboon on Wednesday May 23, 2018 @01:58AM (#17131724)
Oracle DB supports Java stored procedures. I wrote a couple back in the day. I'm not sure we want to go there :P
[ Parent | on HN ]