You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 27, 2023. It is now read-only.
When there are more than 100 table in user's account and a table for a model already exists engine.create_schema() will fail with:
ResourceInUseException: Table already exists: table-name
This happens because in engine.py line 204 the call to:
tablenames=set(self.dynamo.list_tables())
will return 100 first tables and in model_meta.py line 440:
iftablenameintablenames:
returnNone
will miss the fact that the table already exists.
Proposed solution:
For each table to create deliberately validate that it doesn't exist. Like (proto-code):
I think the solution might be easier than that. Old versions of dynamo3 had a default limit on list_tables of 100, but since 0.4.6 the default limit has been removed. Can you try pip install dynamo3>=0.4.6 and see if that fixes your problem?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When there are more than 100 table in user's account and a table for a model already exists engine.create_schema() will fail with:
ResourceInUseException: Table already exists: table-name
This happens because in engine.py line 204 the call to:
will return 100 first tables and in model_meta.py line 440:
will miss the fact that the table already exists.
Proposed solution:
For each table to create deliberately validate that it doesn't exist. Like (proto-code):
The text was updated successfully, but these errors were encountered: