What did you do? ================ 1. Created a postgres user and database 2. export DATABASE_URL=postgres://user:password@localhost:5432/dbname 3. Run tests What happened? ============== Out of 196 tests, 2 errored and 14 failed. What should have happened? ========================== All tests should pass Is there anything else we should know? ====================================== The differences appear to be in instance primary keys. SQLite will re-use auto IDs during a test run, but postgresql assigns incrementing auto IDs, even when wrapped inside a transaction.
:travis - this system will likely run on the cloud infrastructure in 2015. What is the best RDBS to use during development to match deployment?
We're currently running on Heroku, using PostgreSQL on their hobby-basic plan: https://devcenter.heroku.com/articles/heroku-postgres-plans#hobby-tier For a previous project, I used AWS's RDS for PostgreSQL, which took care of backups, software updates, etc.: http://aws.amazon.com/rds/postgresql/ AWS also supports MySQL, but that's gross. PR #12 fixes the tests, and tests against PostgreSQL in Travis: https://github.com/mozilla/web-platform-compat/pull/12
We're fine with either MySQL or Postgres. I'd actually recommend MySQL only because of Aurora recently announced by AWS. It's fully MySQL compatible with significant performance improvements.
Commits pushed to master at https://github.com/mozilla/web-platform-compat https://github.com/mozilla/web-platform-compat/commit/ab3faf64ed58b8173136cf7492622a3553f38de9 fix bug 1095584 - Fix tests when using PostgreSQL https://github.com/mozilla/web-platform-compat/commit/aad1e19c1573d9272db560131dd0f67c213d3278 Merge pull request #12 from jwhitlock/1095584_postgres_tests fix bug 1095584 - PostgreSQL fixes
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.