DMZ 1.7.1 (DataMapper OverZealous Edition)

[eluser]OverZealous[/eluser]
@Jack Scott
Regarding the autoload method: it's going to be called anytime a class is requested that hasn't already been loaded, no matter where that class is called. (It's related to the way PHP loads classes.) Due to the required naming scheme (ie: that every model has to have a unique class name across the entire app, and the file name is the same as the class), it shouldn't ever cause an issue. (You cannot have any other classes with the same name as your DMZ models, just like you can't have any two classes with the same name, anywhere.)

I'm not ready to start worrying about CI 2.0 yet, and I don't have access to EE. Feel free to post it, but I'm probably not going to be worrying about it too soon.

I don't think there is an issue with letting CI load the models, other than if CI loads a model, that model gets instantiated whether or not it is used. If you let DMZ lazily load the models, then only the models needed for that request get loaded. I wasn't going to allow models to be loaded via CodeIgniter, even with the name change, just provide a better error, but I'll think about it. (It's important to realize that DMZ models aren't truly CodeIgniter models - they don't share any code with CI's models, and they work very differently.)