You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
error "There is no primary key here. Update will only use exact matching of the old values of the columns here. Thus, it may update more than one record."
#3005
Closed
Myshiner opened this issue
Sep 9, 2019
· 4 comments
· Fixed by #3379
question:
when i use navicate to connect sharding-proxy, and do double-click the table(any table), it can load all the datas but just threw the errors like "There is no primary key here. Update will only use exact matching of the old values of the columns here. Thus, it may update more than one record."
The text was updated successfully, but these errors were encountered:
I debug Sharding-Proxy source code, when execute a query SQL, it should return column metadata.
But in MySQLColumnDefinition41Packet class, the this.flags = 0 :
this is the table column primary key flag, so the Navicat prompt a error message.
the MySQLColumnDefinition41Packet build by ResultSetMetadata, but ResultSetMetadata don't have primary key info, we can find primary key info in DatabaseMetadata, but it will be a huge change.
project: sharding-proxy
version: v3.1.0 & v4.0.0-RC2
question:
when i use navicate to connect sharding-proxy, and do double-click the table(any table), it can load all the datas but just threw the errors like "There is no primary key here. Update will only use exact matching of the old values of the columns here. Thus, it may update more than one record."
The text was updated successfully, but these errors were encountered: