mleku on Nostr: i've been trying to have some kind of sensible "database drop" functionality in my ...
i've been trying to have some kind of sensible "database drop" functionality in my project for testing purposes and i initially had this funny iteration that went through and deleted everything
this broke two funny records that made the migration thing bomb out and refuse to start
so then i made a thing that iterated and left those two records... but even though i close the db, somehow those delete key operations didn't actually work
and then, finally, i find there is a bulk drop operation, that lets you give a set of key prefixes to drop the damn records
et voila
finally!
this is for the #golang badger key value store... i'm starting to get a bit handy with this thing now, it's a really nice, really fast db with some very neat capabilities for creating indexes (because they can be key-only, and the design separates keys and values to mitigate write amplification in the log-structured (LSM?) key value store
nobody else in key value store dev has bothered to add this feature to any database key value store for any other language... not one... but screw them, because dgraph uses it as it makes their graph database that much better, and it is a really solid excuse for me to say "learn #golang so you can use a decent database with modern features"
just do it... learn golang, you will never regret it, the FUD around go is bizarre
#devstr #deardiary #badgerdb
this broke two funny records that made the migration thing bomb out and refuse to start
so then i made a thing that iterated and left those two records... but even though i close the db, somehow those delete key operations didn't actually work
and then, finally, i find there is a bulk drop operation, that lets you give a set of key prefixes to drop the damn records
et voila
finally!
this is for the #golang badger key value store... i'm starting to get a bit handy with this thing now, it's a really nice, really fast db with some very neat capabilities for creating indexes (because they can be key-only, and the design separates keys and values to mitigate write amplification in the log-structured (LSM?) key value store
nobody else in key value store dev has bothered to add this feature to any database key value store for any other language... not one... but screw them, because dgraph uses it as it makes their graph database that much better, and it is a really solid excuse for me to say "learn #golang so you can use a decent database with modern features"
just do it... learn golang, you will never regret it, the FUD around go is bizarre
#devstr #deardiary #badgerdb