I have a test module with 2 user defined fields. This module is stored in an non primary database in a table with columns. I want to remove one of the fields; however, when I modify the module it throws an error saying ’ cannot modify created. Changing physical schemas is not yet supported’.
I modified the table by deleting the table in the schema. Is there a way to force Corteza to resync or to tell it to ignore this error and proceed? This issue is a major hurdle in using the system for any serious development since changes are bound to happen and one can’t keep on recreating modules every time there is a schema change.