3 ms·

Just another language to use instead of standard pl/pgsql. You already could use other languages - tcl, perl, python, or java, ruby, php and basically any one a

by zalew 15y ago

Just another language to use instead of standard pl/pgsql. You already could use other languages - tcl, perl, python, or java, ruby, php and basically any one as long as you provide the handler and lang support is configured. I don't see why one would code DB procedures in JS though. Are there really many cases where a dba/designer's best known and favorite lang is JS? I doubt that.

willvarfar 15y ago
http://williamedwardscoder.tumblr.com/post/18065079081/cogs-bad#comment-445990171 http://williamedwardscoder.tumblr.com/post/18065079081/cogs-... "The controversy over Node is that it implies developers from the client are piercing into the server. A domain typically full of people that came up from the OS layer. Those people are asking does it really make sense to write servers in a historically client language? (One that as you mention is inherently far slower than historical server languages). People who only know or love that client language have been given a whole new freedom and ability - surely their answer is yes. Why wouldn't it be?" Very well put. And now they can put logic in the DB too. Bravo!
- swasheck 15y ago
  Not sure why you're being downvoted. Though as one of those "data guys" I have actually received my own fair share of the reverse criticism. How could I, as a data monkey, be able to write anything close to clean, sensible code?
mhurron 15y ago
What about a DBA who used to write client side code? What about a developer who is putting proof-of-concept stuff in a dev environment? As you said, this just adds JS as yet another language to write stored procedures for PostgreSQL. There's no real need to disparage choice.
einhverfr 15y ago
I would think with stored procedures in Javascript and JSON as a native type you could mix and match SQL and NoSQL approaches to your heart's content!

by zalew 15y ago

willvarfar 15y ago

http://williamedwardscoder.tumblr.com/post/18065079081/cogs-bad#comment-445990171 http://williamedwardscoder.tumblr.com/post/18065079081/cogs-... "The controversy over Node is that it implies developers from the client are piercing into the server. A domain typically full of people that came up from the OS layer. Those people are asking does it really make sense to write servers in a historically client language? (One that as you mention is inherently far slower than historical server languages). People who only know or love that client language have been given a whole new freedom and ability - surely their answer is yes. Why wouldn't it be?" Very well put. And now they can put logic in the DB too. Bravo!

swasheck 15y ago
Not sure why you're being downvoted. Though as one of those "data guys" I have actually received my own fair share of the reverse criticism. How could I, as a data monkey, be able to write anything close to clean, sensible code?

mhurron 15y ago

What about a DBA who used to write client side code? What about a developer who is putting proof-of-concept stuff in a dev environment? As you said, this just adds JS as yet another language to write stored procedures for PostgreSQL. There's no real need to disparage choice.

einhverfr 15y ago

I would think with stored procedures in Javascript and JSON as a native type you could mix and match SQL and NoSQL approaches to your heart's content!