Re:LoopBack, a new Node.js framework by StrongLoop
by rmgraham on Sunday May 25, 2014 @04:05PM
(#7797383)
Postgres almost warrants its own non-generic ORM. That would actually be kinda cool.
Re:LoopBack, a new Node.js framework by StrongLoop
by hardwaresofton on Sunday May 25, 2014 @05:44PM
(#7797688)
If I understand your comment right, are you looking for something like this:
I haven't done much work with a relational DB from nodejs (I've just used nosql databases that offered relational functionality -- i.e. rethinkdb), but this seems like as good a thing as any for ORM-y stuff with Postgres
Re:LoopBack, a new Node.js framework by StrongLoop
by whatthemick on Monday May 26, 2014 @03:10AM
(#7798979)
There's also Sequelize (http://sequelizejs.com/) which is increasing its focus on Postgres specific features.
Re:LoopBack, a new Node.js framework by StrongLoop
by woah on Monday May 26, 2014 @12:12AM
(#7798671)
The backbone stuff in there kind of made me raise an eyebrow... not sure I really want it.
Re:LoopBack, a new Node.js framework by StrongLoop
by angersock on Sunday May 25, 2014 @05:33PM
(#7797645)
Hmm....
Especially exposing some of the things like intervals, the geographic features, and a lot of their other cool things.
Yeah, I could live with that.
Re:LoopBack, a new Node.js framework by StrongLoop
by enjoyjava on Sunday May 25, 2014 @04:08PM
(#7797394)
Good catch. We support Postgresql, MS SQL Server, and SOAP too.
Re:LoopBack, a new Node.js framework by StrongLoop
by hardwaresofton on Sunday May 25, 2014 @05:46PM
(#7797695)
Great!
I'm actually considering using this in a new project right now - it is very very tempting to think that I could just use this, and have a middle-layer that I don't have to muck with... this would greatly speed up development, I do applaud the team for trying something so ambitious, could be huge
However, the scale of this really worries me. I really like small tools (flask over django, knockoutjs over angular sometimes,etc) -- and this seems like a LOT to take in to a project, sort of hoping it all just works...
Also, why is Postgres support not more prominently stated? It's there, but I had to search for it. And on that note, why is JSON stored in postgres as a varchar? why not use the postgres JSON type (compatibility reasons, maybe?)