SQLite generated columns #6135
SQLite generated columns #6135
Conversation
…instead of table_info
|
Your changes break our test suite apparently. DBAL currently does not offer any abstraction for generated columns. I don't think it's wise to list them if DBAL doesn't know how to handle them. I will at least need a couple of tests that show me that schema introspection and comparison is not broken by generated columns. |
|
Indeed I did some further digging and while for the most part this works to retain columns they are not marked as such and will just be listed as regular columns later on (resulting in unexpected schema changes once again). I'll try to find some time to add proper support for generative columns. |
|
There hasn't been any activity on this pull request in the past 90 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days. |
|
This pull request was closed due to inactivity. |
Summary
The current implementation for SQLite will not list any generated columns due to them being retrieved through the
table_infopragma statement. This causes problems for situations where DBAL is used for schema changes (for example Laravel) where a generated field will get dropped whenever a column gets changed (Laravel uses DBAL for this specific case).table_xinforeturns data the same way but does include the generated columns.