I tried adding a column to a table which is used in a materialized view and received the error
Cannot drop or modify object '%1' because at least one other object ( %2 '%3') depends upon it
In the remarks it says that this is expected for "...a materialized view, that cannot be automatically invalidated." So, what are the criterias which prevent a materialized view from being automatically invalidated?
Request clarification before answering.
SQL Anywhere does not have a mechanism for automatically invalidating/re-materializing any materialized view when an underlying base table is modified. So it's not a question of which materialized views can or cannot be automatically invalidated; none of them can.
SQL Anywhere does, however, have the ability to automatically invalidate and re-establish ordinary views.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 10 | |
| 5 | |
| 5 | |
| 5 | |
| 5 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.