We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
是基于mysql的query_cache机制吗? 还是什么,有具体的原理没?
The text was updated successfully, but these errors were encountered:
SQLExecutor: Map<String, List<JSONObject>> cache; void putCache(String sql, List<JSONObject> list, int type) List<JSONObject> getCache(String sql, int type) void removeCache(String sql, int type) https://github.com/APIJSON/APIJSON/blob/master/APIJSONORM/src/main/java/apijson/orm/SQLExecutor.java
Sorry, something went wrong.
SQLExecutor: Map<String, List> cache; void putCache(String sql, List list, int type) List getCache(String sql, int type) void removeCache(String sql, int type) https://github.com/APIJSON/APIJSON/blob/master/APIJSONORM/src/main/java/apijson/orm/SQLExecutor.java
感谢作者的回答! 简单看了下实现逻辑,是将查到的List缓存起来。这里有个疑问,如果查询的数据表中有更新或者插入,这个缓存其实是感知不到的吧,对于一些需要相对实时但又想缓存部分数据的场景,似乎这个缓存用处不大?
这只是单次会话的缓存,用完即清,不需要感知更新。需要全局的可以重写相关方法,用 Redis 等方案存取
No branches or pull requests
是基于mysql的query_cache机制吗? 还是什么,有具体的原理没?
The text was updated successfully, but these errors were encountered: