Work Around / Avoid "Update or insert of view or function failed because it contains a derived or constant field."

Transact-SQL
6

Yes, I reckon that's it. The CREATE works fine, but I reckon something must be deferred until runtime :frowning:

  1. Agree - Yuck!
  2. That would be a much better solution than using a VIEW instead of a table (feels "cleaner" and easy to jsut REMOVE the SYNONYM when the PATCH runs, which i think is cleaner than having to check if there is a VIEW / TABLE and then deciding which method to do). However, I also have Column Name renames ... so can't catch those with a SYNONYM

Yup, definitely would. I had thought of that and discounted it, but actually if I create an INSTEAD OF TRIGGER when I make the "Forward-Compatibility" VIEW then anything that wants to insert into the NewTableName will actually Work Just Fine.

I'm still a bit torn with whether I should replace the INSERT with an EXEC MySProc. That seems to me to be OK provided that there are literally just one or two instances, but if it turns out to be more then INSTEAD OF TRIGGER would be a much better solution.

For now I have commented the code out :scream: ...

... needs a proper solution though.