So If I use the prepare, it will give the query to the database server to compile it and then it will return the handle. If the function is called in a loop, then it will be in-efficient. In those case we can use prepare_cached, because we are using the same query and no need to compile it again.
I think this is a poor example since if you were executing the same SQL repeatedly in a loop you would prepare it once and execute it many times. The point about prepare_cached is that DBI holds on to the statement handle prepare_cached returns in the connection so even once you've finished your loop (and perhaps even the sub it is in) the statement handle is still available to use for the exact same SQL somewhere else in your program.
In reply to Re^2: dbi: prepare vs prepare_cached -- which is best ?
by mje
in thread dbi: prepare vs prepare_cached -- which is best ?
by sathiya.sw
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |