- 🇳🇱Netherlands daffie
Closing this issue as a duplicate of 🐛 New serial columns do not own sequences Fixed .
PostgreSQL uses sequences to track the current value of a serial column. When a serial column is created, a sequence is automatically created with a naming convention of {table_name}_{column_name}_seq. However, this sequence doesn't get renamed when a column is renamed. Therefore, a sequence belonging to a serial column that is changed by the schema API will no longer be accessible.
For example, I take a serial column called "test_column" and rename it to "test_column_old". The serial will still be called "test_column_old". Then I create a new serial column called "test_column". PostgreSQL will create a new sequence called "{table_name}_test_column_seq1" because "{table_name}_test_column_seq" already exists. This means, when Drupal tries to access that columns sequence, it will access what the schema API knows and not the correct sequence for either columns.
I think we need to add checks to move/delete sequences along with serial columns.
Closed: duplicate
10.1 ✨
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Closing this issue as a duplicate of 🐛 New serial columns do not own sequences Fixed .