Core Auth Library

[eluser]jedd[/eluser]
[quote author="wiredesignz" date="1250475120"]From my experience MySQL VIEW's based on joins are read-only thus inserts or updates are not practical.[/quote]

Hey wiredesignz - yeah, reading through the MySQL 5.0 pages for views is a bit bewildering to me. I get the general idea, but this page is atypically obtuse, I think, compared to the rest of the MySQL documentation.

I gather the change limitation is more to do with views not automatically reflecting table-layout changes to the underlying tables - not something we'd care about, I suspect here.

Bits of the documentation - the FAQ for the views, and things like this quote:

For a multiple-table updatable view, INSERT can work if it inserts into a single table. DELETE is not supported.

... suggest the option to insert into tables presented by a VIEW is do-able.

For our purposes here, I'd reckon that in the majority of cases we'd be mapping a view over a single extant table.

If we wanted to get sophisticated, we could wrap up the C and possibly U calls into a transaction, and do multiple INSERTS (where we're mapping multiple user tables) sequentially. I suspect the same approach would catch D calls. Reads, obviously, sound pretty painless.