mleku on Nostr: ah yeah, this is a good reason for structuring it hierarchically then it's still ...
ah yeah, this is a good reason for structuring it hierarchically then
it's still gonna be quite overhead-heavy but it does make it simpler to make queries to find the parts, since each parameter can relate to a layer
if you change a leaf, you have to change every layer up to the root of the event, so that means verse, chapter, book, and volume events have to all be changed at the same time to modify a verse, but i guess it is what it is
my relay is not bloating up memory that much by keeping a list of whitelisted users over 11k so i think this is fine
it's still gonna be quite overhead-heavy but it does make it simpler to make queries to find the parts, since each parameter can relate to a layer
if you change a leaf, you have to change every layer up to the root of the event, so that means verse, chapter, book, and volume events have to all be changed at the same time to modify a verse, but i guess it is what it is
my relay is not bloating up memory that much by keeping a list of whitelisted users over 11k so i think this is fine