New release branch, v0.8

[Matthew Eernisse]

Gedders,

It's time for a new release. I've cut a branch, and would appreciate a little sanity-checking before I push it out:

https://github.com/mde/geddy/tree/v0.8

Here's the Changelog with the list of what's in it:

https://github.com/mde/geddy/blob/v0.8/changelog.md

Lots of good stuff in there, including the huge refactor of app.js -- definitely want to make sure it doesn't break stuff for existing apps.

If I don't hear anything bad, I'll be pushing this out tomorrow or the next day.

Thanks!


Matthew

[Daniel Erickson]

Awesome, lots of good stuff in there!

Matthew

--
The official community discussion group.
website: geddyjs.org, source: https://github.com/mde/geddy, group: https://groups.google.com/d/forum/geddyjs?hl=en
---
You received this message because you are subscribed to the Google Groups "GeddyJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to geddyjs+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Ben Ng]

You guys did some amazing work this release. My app's tests are passing on 0.8.

[Matthew Eernisse]

Excellent. I'll probably be pushing 0.8 out tonight, unless I see people posting with problems.

[edugg]

nice work as always.

By the way, reading the changelog, Are Eager-loading associations going to work with mongo?

[Matthew Eernisse]

No, it's for SQL only.

Mongo is non-relational and joins are not possible. They recommend denormalization instead:

http://docs.mongodb.org/ecosystem/tutorial/model-data-for-ruby-on-rails/

The API is the same, so it should be easy to switch to Postgres if you want this feature.

[Miguel Madero]

Hi Matthew, 

Nice post, thanks for sharing. I was thinking a bit about this a few weeks ago, but I haven't had a chance to dump some of this ideas into code or even an email. I had some ideas on how to better handle some of these, but I wanted to check how things actually work currently on geddy and have a reference of how things work on rails. Denormalizing single attributes or even arrays is simple, but nested models/documents is tricky (or I might be missing something). 

If I understand correctly, when using mongo, each model will be in it's own collection. hasMany, hasOne or belongsTo will just add FK like references in the right places. I was thinking we should be explicit about this and have an hasManyEmbedded and hasOneEmbedded (belongsTo wouldn't make sense). If we didn't care about backward compatibility, I would make the default embedded and have to opt-out. However, I kinda like the idea of using different base class, it wouldn't make  a lot of sense to use something as an 'EmbeddedDocument' and also to store the exact same structure in it's own collection depending on how you save it. 

What do you guys think? 

Miguel