Open ilyakooo0 opened 4 months ago
This issue also means that it is not always possible to encode all desired changes in a single migration.
Hi @ilyakooo0 👋 , thanks for opening the issue.
The inability to reference objects created in earlier operations in the same migration is tracked in https://github.com/xataio/pgroll/issues/239 as part of the v1 milestone.
It is a significant limitation and one that will need to be removed before a v1.
When I try to reference a table added within the same migration I get the following error:
This is really misleading and results from the way temporary tables are created during a migration.
I think pgroll should ccount for the temporary table names and create the references using temporary table names.