The test WriteTest::testLastInsertIdNoSequenceGiven() does not work if the tested platform supports both sequences and identity columns and when the driver is able to return distinguished information about the last inserted sequence ID and identity column ID.
The problem here is that both sequence IDs and identity column IDs get inserted into the database in the tests before. Therefore a driver that is capable of distinguishing between last inserted sequence and identity column IDs returns the last inserted identity column ID when Connection::lastInsertId(null) is called in this particular test.
The behaviour of Connection:lastInsertId() is very inconsistent throughout the drivers and therefore a true expectation can only be made if the tested platform supports sequences but not identity columns.
fix test for platforms supporting both sequences and identity columns
thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:
We use Jira to track the state of pull requests and the versions they got
template1 as default database for Postgres
Fixes #402 (doctrine/DoctrineBundle#402) by connecting by default to 'template1' instead of the database with the same name as the user (Postgre default in case of no dbname).