Anyhow, it's a matter of taste, but what may appear at first as hieroglyphics actually is straightforward. It's just that concision here means some packed meaning and some assumed knowledge, so you have to know how to read it. In this case, that's an easy trade-off for me.
I'm not familiar with SQLAlchemy, so I find your example equally hard to read, compounded by there being much more code to spelunk through to understand.
Different strokes and all that, though. There's room for plenty of frameworks :)
If you remove few column definition and setup code, it actually boils down to just:
class Article(ArticleColumns):
@property
def users(self)
return self.collaborations.join("user").with_entities(User)
class User(UserColumns):
pass
class Collaboration(CollaborationColumns):
user = relationship("User", backref="collaborations")
article = relationship("Article", backref=backref("collaborations", lazy="dynamic"))
@hybrid_property
def editorial(self):
return self.role == 'editor'
In which you can now do some_article.users.filter(Collaboration.editorial)
which generates similar SQL query as #merge.I mostly wanted to demonstrate that the functionality of Rails' merge() can be considered in other ways that are just as succinct.
There is a database toolkit in ruby-land that allows you do just that! It's called Sequel.
I've built an example, which I deliberately kept as bare-bones and explicit as possible: https://gist.github.com/1aa977a63b7d6a727497
You can also build something similar on top of ARel which backs ActiveRecord.
[1]: http://docs.sqlalchemy.org/en/latest/core/tutorial.html