Skip to content
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

Sync upstream #1

Merged
merged 19 commits into from
Aug 23, 2019
Merged

Sync upstream #1

merged 19 commits into from
Aug 23, 2019

Conversation

bblommers
Copy link
Owner

No description provided.

@bblommers bblommers merged commit d4aa557 into bblommers:master Aug 23, 2019
bblommers pushed a commit that referenced this pull request Oct 3, 2019
h/t @beheh. This patch handles the case when ProjectionExpression looks
like "#1, ..., #10" - the previous code used `replace`, which would make
the resulting projection into "foo, ..., foo0".
bblommers pushed a commit that referenced this pull request Nov 16, 2019
Updating from upstream
bblommers pushed a commit that referenced this pull request Jan 4, 2020
A query fails if it has a space between `begins_with` and `(`,
for example: ```begins_with (#1, :1)```

Fix getmoto#1996
bblommers pushed a commit that referenced this pull request Feb 24, 2020
Merge with spulec/moto
bblommers pushed a commit that referenced this pull request Aug 1, 2020
…to#3206)

When using pynamodb's support for transactions it makes use of of
ExpressionAttributeNames that look like #0 #1 etc. According to

https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.ExpressionAttributeNames.html

And when testing against dynamodb-local these work without issue,
however, when testing with moto they fail.
bblommers pushed a commit that referenced this pull request Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants