Post your controller!

[eluser]Boris Strahija[/eluser]
[quote author="James Brauman" date="1251705590"][quote author="Boris Strahija" date="1251656397"]I think it would be better if you would put your SQL statements into a model. There's a reason why CI is MVC [/quote]
I originally did have them all in model files however I found I was writing methods to select, update, insert and delete things from the database, which to me seems counter-intuitive and a waste of time.

For example I had a method called get() which would take an array of criteria (a key which was the field an value with was the value) and get the content of that record (or records) and return it. But in reality it was just more work than its worth, when I could write the SQL statement in my controller and get just what I need, when I needed it.

I still have some things in my models though, for example I have two tables joined by a pivot table, and one of the methods get the things associated with a record in the other table via pivot table and sorts them.

But its far easier to just leave the select/insert/update/delete functions to the controller.

To me, seperating the view from the logic is absolutely important, but seperating database functions from the controller is only done if there is a reason.[/quote]
I understand that it's easier for you, and I ceartainly won't preach MVC to you It just seems much cleaner code to me when I separate everything in the MVC way, and taht means for me that all data stuff should be in a model. I think it's also important when more than 1 person are working on the project. It can quite easy become a mess if you don't follow the basic rules.