Re: Package proposal

Maxim Antipin wrote:

No, you are wrong. Caches are located not on clients' machines. There are no several copies of cache. All clients use one cache. The only possibility to get error if MySQL will receive two queries 'simultaneously'. One should modify data second should query. Then if they will executed with interval less the 1ms (average time needed to process modification query and update cache storage) then we will get rotten data. But it is problem of all disk caches. Who said that cache files are located on client machines? The last comment was about using multiple webservers, each caching its own copies of the database.

Maybe http://www.php.net/memcache is a better solution.

Yes i can not. But why it bother you :) Common script user usually do not modifies data directly through phpMyAdmin. It just sets up application and runs it. If you are not common user and you modified data bypassing caching mechanism you can just delete cache from disk. That is all you need to invalidate all cache :) I know of many "common script users" who like to modify data through phpMyAdmin.

You are wrong. Function 'mysql_list_tables' is called in cache constructor. But cache constructor is called once when we create DB driver. When driver processes queries it does not call 'mysql_list_tables' function. It is called once the db driver is created, ok - but doesn't the db driver need to be created to process queries?

I want to say that this is not ideal caching solution and it has some restrictions and disadvantages. But it can be useful, at least it is useful for us :) "at least it is useful for us" . So, why pear?