Skip to content

Conversation

sean-krail
Copy link
Contributor

@sean-krail sean-krail commented Dec 4, 2019

_createMigrateTableIfNotExists now works when there are more than 100 tables (DynamoDB has a soft limit of 256 tables per region). Say you have 101 tables table1 through table100 and your migration history table's name is table101, the function thinks the migration history table doesn't exist, tries to create it, and then throws a ResourceInUseException since it really does exist.

Changes

  • renamed _createMigrateTableIfNotExits to _createMigrateTableIfNotExists
  • _createMigrateTableIfNotExists now uses describeTable instead of listTables to figure out if the migration history table already exists. This change was made since listTables uses pagination which defaults to 100 and describeTable can fetch one table by name.

@sean-krail
Copy link
Contributor Author

@noppoMan the travis tests are broken for node v4 and v5, all other versions are working as expected.

@sean-krail
Copy link
Contributor Author

@noppoMan #73 fixes the travis tests

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.

1 participant