Fix Sqlite persister and Behavior locator #1088
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SQLite keeps track of auto-increment fields in an internal table, called
sqlite_sequence
.https://www.sqlite.org/fileformat2.html#seqtab
With this commit,
Propel\Runtime\Persister\SQL\SQLitePersister::readAutoIncrement
methodtakes values from this table, preventing
FOREIGN KEY violation
errors.This commit also provides a test, which failed with previous versions of the persister.
The previous algorithm, to read auto-increment fields, is still used if there's no
sqlite_sequence
table entry, for the given field.