@gh0st
In your example of the car, to produce this as DRY you would store a ‘model’ of the car properties and thier database locations in a model file.
Pull the car ‘model’ and use the fields to carry out the select and data return in your DB query and again to populate the fields in the view.
This way, when you change the properties of the car, you only have to change the ‘model’ and the DB query and view will change automatically.
Of course, you would still need to add the relevant fields to the relevant tables.
This technique is handy for building generic forms - I am working on one at the moment, if I ever get a chance to finish it, I will publlish it in the wiki
DRY is possible with CI, but somtimes you need to make one more lateral thought step.
obiron
Sorry to butt in here, but that sounds really cool. If anyone has some working code examples or tutorials, I’d really enjoy seeing them.
Cheers!