[eluser]BrianDHall[/eluser]
I am not aware of anything in the specification of MySQL views that makes them different to DMZ than a regular table. You could, theoretically, create a DMZ model that pertains to a MySQL View instead of a Table. I'm not really sure its a good idea to build an application in this way, but pick your poison.
So, feel free to give it a try. DMZ nor CI has any special support for Views, as they are very platform specific in behavior and the only thing really different about them is how they are defined at the database administrative level - and CI/DMZ, other than the Database Forge functions provided in CI, doesn't really get into this realm very much.
Thinking more about it, I don't see why you couldn't, but you should be real sure its necessary and you couldn't just as easily (or more easily) utilize an Advanced Get function available in DMZ and get a perfectly good efficient single query.
And you have to be sure it is sufficiently useful that you aren't just creating a database structure to save a few lines of code here and there. You'll be adding a degree of difficulty to maintenance, it may be less clear to others how the program is really working, and there may be caching conflict issues (as PHP and Apache-based caching solutions and query caching through CI/DMZ will not understand that a given View is just a JOIN on other tables, etc).
