You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2019/12/26 06:42:19 UTC
[GitHub] [incubator-shardingsphere-example] songjiesdnu opened a new issue
#202: By default, in sharding-jdbc,
"select ...... for update" is routed to slave datasource.
songjiesdnu opened a new issue #202: By default, in sharding-jdbc, "select ...... for update" is routed to slave datasource.
URL: https://github.com/apache/incubator-shardingsphere-example/issues/202
## Question
In our application, there are some uses of "select ...... for update", when we use sharding-jdbc, these sqls is routed to the slave datasource, which is set read-only, and thus these sqls cannot be exeucted. We solve the problem by using HintManager and setMasterRouteOnly。
**My question is, why sharding-jdbc do not route "select ...... for update" to master datasouce by default?**
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-shardingsphere-example] terrymanu commented on issue
#202: By default, in sharding-jdbc,
"select ...... for update" is routed to slave datasource.
Posted by GitBox <gi...@apache.org>.
terrymanu commented on issue #202: By default, in sharding-jdbc, "select ...... for update" is routed to slave datasource.
URL: https://github.com/apache/incubator-shardingsphere-example/issues/202#issuecomment-571029010
Closed for no response anymore
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-shardingsphere-example] terrymanu closed issue #202: By
default, in sharding-jdbc,
"select ...... for update" is routed to slave datasource.
Posted by GitBox <gi...@apache.org>.
terrymanu closed issue #202: By default, in sharding-jdbc, "select ...... for update" is routed to slave datasource.
URL: https://github.com/apache/incubator-shardingsphere-example/issues/202
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-shardingsphere-example] terrymanu commented on issue
#202: By default, in sharding-jdbc,
"select ...... for update" is routed to slave datasource.
Posted by GitBox <gi...@apache.org>.
terrymanu commented on issue #202: By default, in sharding-jdbc, "select ...... for update" is routed to slave datasource.
URL: https://github.com/apache/incubator-shardingsphere-example/issues/202#issuecomment-569376191
What is you version?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services