not onyx, i know it is, that's why i thought it's promising. i meant granite
it doesn't look like it
Vlad Faust
@vladfaust
Well, in my humble opinion, Onyx::SQL has the best type-safety and overall design among the others :D
Joakim Repomaa
@repomaa
have you seen avram?
Vlad Faust
@vladfaust
Yes, I've read it docs
Joakim Repomaa
@repomaa
ok
i think it's superb
Vlad Faust
@vladfaust
You should definitely give it a try
Joakim Repomaa
@repomaa
i have
but only with the whole framework
which is a bit overblown for most of my usecases
Vlad Faust
@vladfaust
I'm sure it is possible to use avram separately
Joakim Repomaa
@repomaa
yeah should be
Vlad Faust
@vladfaust
BTW, you've said "Onyx has no support for txs", but that's not true. It does have it, I've managed to change repo's db to single tx even without those patches
Joakim Repomaa
@repomaa
yeah but that's more like a hack :D
i'm looking for builtin support by the api like Onyx::SQL.transaction { ... }
Vlad Faust
@vladfaust
Does this really change anything? :thinking:
But I get you, alright
Joakim Repomaa
@repomaa
of course it does. error handling etc all capsuled into the orm
i don't want to manually have to commit/rollback the tx
i guess using the block variant of DB#transaction would help with that
hm i also don't quite understand this: yes, because onyx/onyx is a higher-level framework, and onyx/sql is an ORM
isn't an ORM exactly the place where you'd expect to find transaction logic? :D