3 ms·
Yea I started to bring up the existing ticket for grouping on the dev list and ask what people thought about it. I also ended up writing a very tiny transforme
by leetrout 6y ago
Yea I started to bring up the existing ticket for grouping on the dev list and ask what people thought about it.
I also ended up writing a very tiny transformer function and using that directly because core only has a couple supported casts and I needed Postgres timestamp types so I could extract and rollup on the year / month / day. That gave me some insight in to some of the patterns in use in “lower level” Django differ from the expressiveness / composability of SQLAlchemy.
- true_religion 6y agoSQLAlchemy has a great architecture, but it comes at the expense of being tied to the use case of accessing a relational database. Django models are more abstract and anemic in querying, but it means you can use the same API and write access layers for non SQL databases. At work, we have an in memory database, and Elastic Search all queried in an identical way to the Postgres models.
- jsmeaton 6y agoI’d be super keen to see your ElasticSearch model implementation if you’re allowed to share it? For what it’s worth, I dislike the unit of work model that SQLA uses, but the layered architecture is enviable.