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
很多场景下需要指定少数方法读从库,这样的话一个 @Usemaster 注解不能满足需求。是否应该考虑通过增加一个 @UseSlave 注解,或者 @Usemaster 增加一个属性的方式来指定该方法走从库读,从而增加灵活性?现在查询默认全部走从库,是否不利于扩展?
The text was updated successfully, but these errors were encountered:
@UseSlave 其实没有必要,默认读就是走从库的
Sorry, something went wrong.
如果想要默认走主库读(从库读少)的话,对源码的改动成本会比较高。那是否考虑将获取数据源的方法进行抽象,允许用户自定义?
No branches or pull requests
很多场景下需要指定少数方法读从库,这样的话一个 @Usemaster 注解不能满足需求。是否应该考虑通过增加一个 @UseSlave 注解,或者 @Usemaster 增加一个属性的方式来指定该方法走从库读,从而增加灵活性?现在查询默认全部走从库,是否不利于扩展?
The text was updated successfully, but these errors were encountered: