[eluser]Conerck[/eluser]
[quote author="Mosselmaniac" date="1266793169"]How do you handle this in practise? You model a new attribute to an existing entity in your database, jump to the representing model, and add it there too? Do you think there is much overhead there? Should this be a reason for me NOT to use DMZ?[/quote]
In DMZ you would only have to touch your database table. The model classes work with PHP's magic functions for getters and setters so you don't need to re-declare the fields in the model class (unless you want/need some validation rules for that field) and you can just start accessing the new attribute in your code right away.
This is somewhat of an advantage for rapid developement, in my opinion, but it also has it's drawbacks. For example you can't rely on code completion in your IDE to make sure that you spell the field names correctly and so on.
But as Phil said, the initial setup and model configuration time should be secondary to your decision, unless you are just looking at hacking up a quick prototype / proof-of-concept. After all, you generally spend more time writing actual application logic and algorithms than defining and changing your models.
You should carefully look at requirements and the feature list of your application. If you just need a simple and reliable way to access some relatively simplme structured data objects, go for CodeIgniter. If you plan on having a more complex database design with alot of deep linked relationsships and/or need complex queries that require alot of manual query optimization or unusual structures and joins you might want to look at a more complex framework that is better at supporting those things.
