-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
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
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
Comments
All the tables do have primary key. |
I am glad to finish it. |
I debug Sharding-Proxy source code, when execute a query SQL, it should return column metadata. this is the table column primary key flag, so the Navicat prompt a error message. the Is this a good way? |
* fixes #3005, QueryHeader add primaryKey, nullable, autoIncrement, signed field. * add apache license (#3005) * fixes code review.(#3005) * fixes column name.(#3005) * add test case.(#3005) * add QueryHeader test case.(#3005) * fixes checkstyle.(#3005) * fixes param name, nullable -> notNull.(#3005)
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: