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/10/14 06:26:20 UTC

[GitHub] [incubator-shardingsphere] liusf1993 edited a comment on issue #3211: Statement "SELECT GET_LOCK('lock10086')" doesn't work as expected

liusf1993 edited a comment on issue #3211: Statement "SELECT GET_LOCK('lock10086')" doesn't work as  expected
URL: https://github.com/apache/incubator-shardingsphere/issues/3211#issuecomment-541517511
 
 
   > Do we talk about horizontal sharding?
   
   I'm sorry for using inappropriatethe case, which made us be involed into distributed lock.
   My point is on adding default database support for sql without tables.
   Let me describle my case agnin:
   I have two db `db1` and `db2`.  `db1` ows table `t1`,`t2`,`t3`, function `f1`,  and  `db2` only onws `t2`. 
   Only table  `t2` was in partition, so I want sql related to  `t1` , `t3`, `f1` to be executed on db1, only `t2` be executed on `db1` and `db2` according to it's condition. I use the configuration `spring.shardingsphere.sharding.default-data-source-name`, now sql related to  `t1` or 't3` was executed on `d1` as expected, but `f2`'s execution was in random.

----------------------------------------------------------------
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