mleku on Nostr: so, a long story short my attempt to create a pubkey index revealed that it is very ...
so, a long story short
my attempt to create a pubkey index revealed that it is very difficult to create two table (join) operations in a key value store unless you designed it that way from ground up
i have forked that work onto a side branch, it sorta works, but because it's running database View closures inside other database View closures it blocks completely
it seems like to make this work i would have to create a worker thread that you send requests for lookups and it runs these in a separate thread while the primary thread waits for the result
it also caused a general massive amount of channel blocking in general that made the import quite slow, maybe half as fast as before, and the export was snail's pace, not as bad as completely deadlocked with the query but ok, to achieve this i have to refactor what i have inside the actual ...
ooh, that's all i have to do... these lookups need to be written to accept a transaction instead of wrapping another one
ok... maybe i haven't quit yet
just gotta get rid of a bunch of closures i guess
i really want this because it's incredible seeing what it does to follow event sizes
my attempt to create a pubkey index revealed that it is very difficult to create two table (join) operations in a key value store unless you designed it that way from ground up
i have forked that work onto a side branch, it sorta works, but because it's running database View closures inside other database View closures it blocks completely
it seems like to make this work i would have to create a worker thread that you send requests for lookups and it runs these in a separate thread while the primary thread waits for the result
it also caused a general massive amount of channel blocking in general that made the import quite slow, maybe half as fast as before, and the export was snail's pace, not as bad as completely deadlocked with the query but ok, to achieve this i have to refactor what i have inside the actual ...
ooh, that's all i have to do... these lookups need to be written to accept a transaction instead of wrapping another one
ok... maybe i haven't quit yet
just gotta get rid of a bunch of closures i guess
i really want this because it's incredible seeing what it does to follow event sizes