Cost of INSERT rules

Hi folks,

I really like the idea of exclusively using views as interfaces
to the applications (each app has its own view, tuned for the
app's access patterns). So, in my model, of course inserts and
updates also happen through views, also more complex operations
could be triggered through view writes.

But for some strange reason, my apps seem to produce high load
on the server. So either I'm just too stupid for proper schema
design or the view approach is really slow.

What exactly does happen behind the scenes if I update some
row in a view ? Does it end up in an full view query before
doing the update ?

cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------