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 2020/04/06 10:39:25 UTC

[GitHub] [incubator-shardingsphere] rimal edited a comment on issue #4822: No value specified for parameter 1

rimal edited a comment on issue #4822: No value specified for parameter 1
URL: https://github.com/apache/incubator-shardingsphere/issues/4822#issuecomment-609713098
 
 
   @terrymanu I am actually facing a similar issue after upgrading from 3.1 to 4.0
   
   It is not failing for all entities. One difference which I could find for the entity for which it is failing is, that in `InsertSQLStatementContext`, `insertValueContexts` is empty. This lead to the parser to expect all column values to be there in the insert query, but actually, all columns are not there in insert statement executed by code.
   
   In my case, `id` is auto-generated and the insert query does not have `id` column at all. But the parser is expecting value for this as well and giving an error for `no value specified for parameter`

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