Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Update delete is down to 400 ms, still too much
asgs98755dAre deletes happening so often in your project?
But clients have a possibility to apply "templates" which triggers delete of "curently applied template" and all manual data entered.
And they have ability to do it in bulk on a 1000+ objects in 1 click.
I'm working to move all of that in async mode.
That usually happens in the first couple of months of implementation where they are testing different templates (And ofc, they don't test on 1 object but on multiple thousands)
Update : Delete down to 9 ms. I can breath now
Many DBs support an DELETE JOIN.
Which does what it says: Deleting from multiple tables by using JOINs.
When associations come into play, this becomes a crucial thing, as u nuke everything in one DDL operation.
Just make sure the WHERE part is safe or good bye all tables. XD
I found a middle ground finally.
Delete is still around 50ms, but all logic is handled.
I think it’s more of database structure / indexes issue right now and I don’t have time allowed for that research.
But we should have a DB expert consulting soon. I’ll put that in his/her todo list.