Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am new to CI. Before I had worked extensively in RoR and Symfony.
I am unable to understand why exactly CI provides Library and Models. Most of the CI code I examined generally used Library as a Wrapper around Model. Models are exclusively kept for talking to database.
Can someone throw light on this ?
There are probably other schools of thought on this, but for me it’s as follows:
Models
Models are tightly coupled to your application, making direct references to your DB schema/architecture/file paths etc.
Libraries
Libraries are loosely coupled. They should be treated like 3rd party add-ons and should make no assumptions about your app or your system. You should be able to “drop in” libraries at will with a minimum amount of configuration. Indeed, the opposite should be true, items in your library folder should be able to be dropped into any other CI application.