Re: cacheing problem
On 28/03/2005, David Nicol wrote: I am using dbd::mysql on activestate perl 5.8. When I select a row in my program, change the row using the mysql administrator tool, and select the row again in the program, the results are not changed. I can get the new data by selecting a different row, then selecting the changed row again, then I get the new results, but running the same select gives a stale result. Would you care to give some more information, and show the code you use? What mysql administrator tool are you using? I cannot reproduce your problem when I change a record with mysql.exe in between two execute-fetch-finish cycli on the same prepared statement. -- felix
Re: cacheing problem
It appears that DBI/DBD is caching the results. How can I disable this? the problem was not in DBI. In case anyone else has this non-problem, my PEBKAC was that user-provided data, which was current with the previous fetch, was replacing the data from the newer fetch. Disabling this for the special case of reloading from the database solved the problem.
cacheing problem
I am using dbd::mysql on activestate perl 5.8. When I select a row in my program, change the row using the mysql administrator tool, and select the row again in the program, the results are not changed. I can get the new data by selecting a different row, then selecting the changed row again, then I get the new results, but running the same select gives a stale result. The result is the same regardless of if I use placeholders or not, if I use a persistent statement handle or make a new one, if I use a persistent connection or call dbi-connect for each select, and is not affected by using 'SELECT SQL_NO_CACHE' instead of 'SELECT.' It appears that DBI/DBD is caching the results. How can I disable this? -- David L Nicol You don't know how to maintain a station wagon either!
