Hi, We use storm in a project and we figure out that storm made an update query for each result of a select, that make it extremely slow when we work on table containing million of entries.
What is the best way to avoid the updates after select and why updating the table after select, i.e making action that the user never ask and launching an update on data that are not modified. I don't really get the reason, if there's one, or is it a configuration problem in our application? Actually we set something like this in our code but need to implicitly set it when we notice some slow pages: # if implicit flushes enabled, unnecessary update will be executed by storm. db.block_implicit_flushes() Thanks for any advice or help. -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
