1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
Do you use ExecuteSqlCommandInput or ExecuteStatementCommandInput to prepare and submit your statements ? If you don't use the latter, please, switch to it and try to replicate the example of https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/dynamodb/command/ExecuteStatementCommand/
Best,
Didier
Relevant content
asked 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 10 months ago

Hi Didier We always use the
ExecuteStatementAPI operation. And we didn't change anything in the calls or the code sorrounding them. The only change, as I mentioned, was moving from serverless v1 to serverless v2.For now the only thing that is working for us is sanitizing the input ourselves and sending the raw SQL, since parameters don't seem to be working at all.
Our engine version is 8.0.mysql_aurora.3.08.0 . If you can get any call at all working with parameters in this engine version, please let us know how you managed to do it. We tried many things but nothing seems to work.
So, apparently, it's a breaking change on MySql, not on the data API. We used parameterized queries for creating db users dynamically in our IaC. Apparently, MySQL 8 doesn't accept a '?' after an 'IDENTIFIED BY', even though this worked in 5.7. According to the documentation in mysql.com this should work, but there seems to be some obscure implementation detail that prevents this from working properly anymore.
One would always like to parameterize values in queries, especially passwords... but anyway, you can disregard as it's not related to AWS.
Hope to help others finding this issue.