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? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
大神~请教一个问题....access,resquest必须都加载再服务内存中吗,服务默认查询最多100条,在什么都不重写的情况下内存中REQUEST_MAP,ACCESS_MAP是不是也只能有100条,若这俩表后期数据量大了怎么处理呢,重新查询最大条数,全部加载在内存中会不会有问题呢?尤其是我现在用的resquest表数据量有点大呢
The text was updated successfully, but these errors were encountered:
必须,最新的几个版本对 Access, Request 等在 AbstractSQLConfig.SYSTEM_ACCESS_MAP 中的表名不做查询数量限制 https://github.com/Tencent/APIJSON/blob/master/APIJSONORM/src/main/java/apijson/orm/AbstractSQLConfig.java#L878-L881C3
这里 Log.DEBUG == false 应该去掉,毕竟上线前要 Log.DEBUG = true 减少日志打印等,会导致上线后初始化加载 Access, Request 表记录仍然限制最大 Parser.getMaxQueryCount(默认 100)。
然后给 APIJSON-Demo 提交 PR 贡献,谢谢,开源要大家一起参与贡献才会更美好~
提 PR 贡献代码的步骤可参考: https://github.com/Tencent/APIJSON/blob/master/CONTRIBUTING.md#%E4%B8%BA%E4%BB%80%E4%B9%88%E4%B8%80%E5%AE%9A%E8%A6%81%E8%B4%A1%E7%8C%AE%E4%BB%A3%E7%A0%81
Sorry, something went wrong.
Update AbstractSQLConfig.java
f0b16a1
这里 Log.DEBUG == false 应该去掉,毕竟上线前要 Log.DEBUG = true 减少日志打印等,会导致上线后初始化加载 Access, Request 表记录仍然限制最大 Parser.getMaxQueryCount(默认 100)。 (摘自 Tencent#640)
Successfully merging a pull request may close this issue.
Description
大神~请教一个问题....access,resquest必须都加载再服务内存中吗,服务默认查询最多100条,在什么都不重写的情况下内存中REQUEST_MAP,ACCESS_MAP是不是也只能有100条,若这俩表后期数据量大了怎么处理呢,重新查询最大条数,全部加载在内存中会不会有问题呢?尤其是我现在用的resquest表数据量有点大呢
The text was updated successfully, but these errors were encountered: