Subject | BUG:"cannot update read-only view" with triggers! |
---|---|
Author | lisovnew <lisovnew@yahoo.com> |
Post date | 2003-01-19T16:17:09Z |
When I define a view and triggers on it, and I do not want default
action to take place, I use workaround mentioned here earlier - join
with rdb$database (or "distnct" - anything to make view read-only).
Everything goes fine until one happy moment when I receive "the
object of the insert,update or delete statement is a view for which
requested operation is not permitted. cannot update read-only
view '...'".
There has been a lot of posts on this subject, but still no solution;
moreover, I get this message when I try to SELECT from this view or
any other dependent on it! I can somehow overcome this trying to
select from independent views and then again from dependent, but when
I close connection and connect again, the error repeats. It has
become a nightmare - I can't do anything: simple select, metadata
change, backup - all throws error!
Anybody knows the cause and workaround? Please help me, cause the DB
is simply not working at all!
action to take place, I use workaround mentioned here earlier - join
with rdb$database (or "distnct" - anything to make view read-only).
Everything goes fine until one happy moment when I receive "the
object of the insert,update or delete statement is a view for which
requested operation is not permitted. cannot update read-only
view '...'".
There has been a lot of posts on this subject, but still no solution;
moreover, I get this message when I try to SELECT from this view or
any other dependent on it! I can somehow overcome this trying to
select from independent views and then again from dependent, but when
I close connection and connect again, the error repeats. It has
become a nightmare - I can't do anything: simple select, metadata
change, backup - all throws error!
Anybody knows the cause and workaround? Please help me, cause the DB
is simply not working at all!