production schema file has been renamed

Created by: magaliruffier

Requirements

• Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion;
• Review the contributing guidelines for this repository; remember in particular:
  • do not modify code without testing for regression
  • provide simple unit tests to test the changes
  • if you change the schema you must patch the test databases as well, see Updating the schema
  • the PR must not fail unit testing

Description

Using one or more sentences, describe in detail the proposed changes. In the production repository, tables.sql has been renamed to table.sql The script has been updated to pick up the correct file

Use case

Describe the problem. Please provide an example representing the motivation behind the need for having these changes in place. Production database are automatically picked up by the script with the correct schema file

Benefits

If applicable, describe the advantages the changes will have. The script works for production databases

Possible Drawbacks

If applicable, describe any possible undesirable consequence of the changes.

Testing

Have you added/modified unit tests to test the changes? NA

If so, do the tests pass/fail? Local runs of the script now work on production databases

Have you run the entire test suite and no regression was detected?