Alice Averlong🏳️⚧️Is there something like mongodb/couchdb that does the sqlite philiosophy of an in-process database that's just saved out to a file?
I need to convert a python program to store some data in a database and I'd rather not deal with SQL.
I mean I could always build a small wrapper around an SQLite database I stuff JSON into
but I'd rather not have to
I just stared at my database schema and went "I don't really want to write another INSERT (...) INTO TABLE_BLAH VALUES(?,?,?); statement. I've done my time
Hugo Mills@foone This is the thinking that leads to the eldritch horrors of ORM frameworks.
@darkling yeah I messed with those once in college and my reaction was "why would I do this, I can just write SQL?"
Solar Granulation@foone I keep getting ads for some AI BS with a tagline like "write SQL you'll love" and just, what? No. Fuck off.
I write my own SQL tysvm. And it's good SQL that does the job as efficiently as the gods-awful database I work with allows.
I reduced overhead by 99.6% using SQL that I wrote.
I just detest this trend. It's mind numbing.
... got a bit ranty there, sorry.
LisPi@darkling @foone I don't think so, in better languages it leads to things like these. The sheer instability of Python is probably why no one has bothered.
Persistent objects predate SQL as a concept.
"why would I do this, I can just write SQL?"
As for why? It can outperform SQL<->object conversion (including when you do it manually with optimizations an ORM couldn't safely do) by magnitudes when done well.
