4 ms·
I was starting to work on my own project just this week to deal with the exact same issues and use cases. Excited to check this out and see how it evolves! Thi
by publicfig 8y ago
I was starting to work on my own project just this week to deal with the exact same issues and use cases. Excited to check this out and see how it evolves!
This could absolutely be my own misunderstanding, but you mention that it's explicitly not an ORM, but reading through the docs, it seems like the collections and querying aspects of this project are just that. It actually seems like most of what this project's scope seems to be is to be used as an ORM (which I personally am fine with). Can you elaborate on that at all?
- ShishKabab 8y agoHey, Vincent (author of article) here! Indeed it's a fine line, but ORMs give you objects with methods that allow you to modify or further query the database, like User.save() or User.objects.find(). This is for me the distinction, and in Storex you get data objects back, but all the manipulation happens through one object, the StorageManager.
- joshribakoff 8y agoSo its a data mapper instead of active record, but still an ORM.
- ShishKabab 8y agoAh, thanks for pointing that out. Will read up on my terminology ;)