DBAL-653: [GH-402] Fix WriteTest for platforms supporting both sequences and identity columns #1872

doctrinebot opened this Issue Nov 6, 2013 · 2 comments

2 participants


Jira issue originally created by user @doctrinebot:

This issue is created automatically through a Github pull request on behalf of deeky666:

Url: #402


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.


Comment created by @doctrinebot:

A related Github Pull-Request [GH-402] was closed:


Issue was closed with resolution "Fixed"

@beberlei beberlei was assigned by doctrinebot Dec 7, 2015
@doctrinebot doctrinebot added this to the 2.5 milestone Dec 7, 2015
@doctrinebot doctrinebot closed this Dec 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment