A brand new tutorial about how to use Doctrine as a CI’s plugin :

http://www.phpandstuff.com/articles/codeigniter-doctrine-from-scratch-day-1-install-and-setup

It can give ideas ? Nope ?

Thanks for linking to my article

Writing the 3rd episode right now.

Hmm.. seems interesting

Good. Thanks.

For those interested, 3 more articles have been posted:

Day 2 - The Basics
http://www.phpandstuff.com/articles/codeigniter-and-doctrine-from-scratch-day-2-the-basics

Day 3 - Signup Form
http://www.phpandstuff.com/articles/codeigniter-doctrine-scratch-day-3-user-signup-form

Day 4 - User Login
http://www.phpandstuff.com/articles/codeigniter-doctrine-scratch-day-4-user-login

a good series, thanks lane4.

@lane - I like the clean code you get in the controller by putting the form_validation in a function(_submit_validate()). I’m going to nick that idea. Great stuff!

Great! Thanks!!

Thanks everyone.

Day 5 and Day 6 have been posted, and more of them are coming very soon.

You’ve done a huge amount of work here and I’m sure it’s greatly appreciated by the community.

From my experience using MVC I’ve concluded that it’s not such a good idea to use any data objects in the controller directly.

Doing this then requires all of your application business logic to be in the controller also when it should really be in your models.

The model should encapsulate the Doctrine objects rather than being replaced by them. Even your diagram (in Part 1) shows business logic being in models but your code examples don’t.

Maybe at some point you could give examples of how a model might encapsulate the Doctrine data objects. Thanks.

wiredesignz - 17 November 2009 02:37 AM

You’ve done a huge amount of work here and I’m sure it’s greatly appreciated by the community.

I’m beginning to believe that it’s not such a good idea to use any data objects in the controller directly.

Doing this then requires all of your application business logic to be in the controller also when it should really be in your models.

The model should encapsulate the Doctrine objects rather than being replaced by them. Even your diagram (in Part 1) shows business logic being in models but your code examples don’t.

Can you be more specific? I am open to suggestions.

I thought that was specific.

Business logic is that logic that makes your application function and is not related to the request, input validation or the response.

The business logic is that which might ensure a user does not register with a username of `Administrator` or that some monetary value when multiplied by some other value does not end up being a negative number etc.

Your models in an MVC context, are supposed to provide this logic. Your data objects should be encapsulated by the model and used in context of the application business logic.

hi there,

just want to ask if ORM support xampp? haven’t tried yet ORM. :D

thanks

wiredesignz - 17 November 2009 03:05 AM

I thought that was specific.

Business logic is that logic that makes your application function and is not related to the request, input validation or the response.

The business logic is that which might ensure a user does not register with a username of `Administrator` or that some monetary value when multiplied by some other value does not end up being a negative number etc.

Your models in an MVC context, are supposed to provide this logic.

Doctrine does have support for Data Validation, and it’s actually more extensive than the CI form_validation class. And it also supports custom validators, where you could for example check for special usernames like (‘Administrator’) as you just mentioned.

I am already planning on making that part of an upcoming episode.

The thing is, I just can’t present all the concepts at once in the very first Model I create in the tutorials. I need to go at a certain pace, as these are meant to be readable by beginners in CI and Doctrine.

Thanks for bringing it up though. If you have any other specific suggestions let me know.

kikz4life - 17 November 2009 03:18 AM

hi there,

just want to ask if ORM support xampp? haven’t tried yet ORM. :D

thanks

It should work, as long as PDO is enabled with MySQL support (unless you want to use a different db driver).

Just to be clear, form (input) validation in the controller is not the same thing as data validation in your model.

The controller checks and cleans the incoming data and ensures that each field meets a minimum requirement. It should not try to check if the data values are suitable for use by the application.

ie: A login form with username and password should be form validated only to ensure the fields exist and are minimum length etc. Your business logic in the model should then make the comparisons and verify the actual values submitted and give a result back the controller so it knows how to respond to the user input.