I encountered the error in v0.24 and was able to reproduce it in v0.25 also.
Do you have any temporary workaround ideas for fixing that constraint expression until the issue is fixed? If I choose the "Continue" option in the alert, I just see a blank view. Whenever I try to open the structure of that table, I get a similar "Internal Error" alert. But, evidently, this throws an exception when the column name is nonexistent.Īlso, when I restart Postico after the crash, I can't go back into my table to correct the constant expression. Normally, this is fine because a CHECK constraint expression should only involve existing column names. Note that the worker_count column is of type smallint.įrom the looks of the error (see below), some type of loop isn't stopped before going beyond the bounds of the mutable array that holds the column names. I tired to add a CHECK constraint to the worker_count column by clicking the "+" button, selecting "Check.", and entering the expression workers_count >= 0. For example, I have a table with 12 columns: Postico will encounter an "Internal Error" when a user tries to add a CHECK constraint to a column if the column name in the expression does not exist in the table.
0 kommentar(er)
