-
Notifications
You must be signed in to change notification settings - Fork 16
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
partiQL Support? #75
Comments
It could be that partiQL is generating a query which is not supported? For example transactions are not yet supported by dynalite, nor are streams. |
@mikewolfd it's been a while since this was opened, but do you happen to remember if you were able to get around it? I just hit this issue, not sure what would be incorrect about the PartiQL statement I'm trying to run as a dummy test... const statement = {
Statement: `SELECT * FROM "MyTableName" WHERE id='${someId}' AND typeId='${someTypeId}'`
};
await ddb.executeStatement(statement).promise(); The same type of select statement works just fine from the AWS console. I've tried every which way I can think of to change single vs. double quotes, no quotes, etc. but still get an Just updated to latest |
@Jack-Barry Did you find a way to work around? I'm at your situation now. |
@khoaleanhvn I never did, ended up punting on using PartiQL, partly because of this issue |
Same here, tested a very simple query directly using |
Hello,
Does this package support running queries using the partiQL statement execution syntax? I'm trying to do it now but am running into
UnknownOperationException
errors.The text was updated successfully, but these errors were encountered: