SqliteSchemaManager::createForeignKey drops the previously added FK

[mvorisek]

Bug Report

Q	A
Version	3.3.7

Summary

AbstractSchemeManager::createForeignKey() method is intended to ADD a new foreign key. If there are already some, they must be kept (or dropped and readded, if platform requires).

Current behaviour

For Sqlite (SqliteSchemaManager), currently, the existing FK is dropped, and after the table is altered, ONLY the new foreign key is present.

How to reproduce

1. create simple table with 3 integer columns a, b, c
2. add FK from column b to a
3. add FK from column c to a
4. notice, FK from step 3 is created, but FK from step 2 is gone

Expected behaviour

FK is correctly added and all existing FKs retained as for all other DB vendors.

[mvorisek]

I close this issue, as one source of this issue is SqlitePlatform::supportsForeignKeyConstraints() returning false for DBAL 3.3.x. In DBAL 3.4, I expect this issue be not present.

related PRs #5409 and #5427

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.