Comments on: Custom Propel Criteria Tips http://blog.mirthlab.com/2007/12/11/custom-propel-criteria-tips/ fortune favors the bold Mon, 08 Sep 2008 10:30:21 +0000 http://wordpress.org/?v=2.6.1 By: Markus http://blog.mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-10 Markus Thu, 13 Dec 2007 16:06:20 +0000 http://mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-10 Hi Mark, I think a Propel Behavior would not be the right direction for your case.. This feature should be implemented directly in the criteria, so it can be used with all classes of your domain model.. (This features is independet from specific model classes) Hi Mark,

I think a Propel Behavior would not be the right direction for your case..
This feature should be implemented directly in the criteria, so it can be used with all classes of your domain model.. (This features is independet from specific model classes)

]]> By: Mark Quezada http://blog.mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-9 Mark Quezada Wed, 12 Dec 2007 19:55:47 +0000 http://mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-9 Markus, I think that's a good idea. It might make even more sense though to make it a Propel Behavior so that every object in your model can have the orderByRand() method without writing any additional code. Markus,

I think that’s a good idea. It might make even more sense though to make it a Propel Behavior so that every object in your model can have the orderByRand() method without writing any additional code.

]]> By: Markus http://blog.mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-8 Markus Wed, 12 Dec 2007 16:40:50 +0000 http://mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-8 you should better subclass the propel criteria and add a orderByRand() method or sth like that.. so you only have one place where you have to change the code, if you move from one dbtype to another. you should better subclass the propel criteria and add a orderByRand() method or sth like that..

so you only have one place where you have to change the code, if you move from one dbtype to another.

]]> By: Dave http://blog.mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-7 Dave Wed, 12 Dec 2007 14:35:27 +0000 http://mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-7 I fully agree with you, Mark. I never switched the database during a project - and honestly, those small adjustments like changing some SQL queries would net be the most problematic part in the migration process. I fully agree with you, Mark. I never switched the database during a project - and honestly, those small adjustments like changing some SQL queries would net be the most problematic part in the migration process.

]]> By: Digital Base http://blog.mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-6 Digital Base Wed, 12 Dec 2007 11:36:28 +0000 http://mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-6 Very nice tip ! Thanks alot ! I didn't know about those random criteria Very nice tip ! Thanks alot !
I didn’t know about those random criteria

]]> By: Mark Quezada http://blog.mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-5 Mark Quezada Wed, 12 Dec 2007 08:53:56 +0000 http://mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-5 Yeah, that may be a disadvantage, but really, how often do you switch database types in the middle of a project? Database abstraction is a great selling point for tools like Propel, but I think the reality is that it's highly unlikely that most people will ever switch a project over to a new database once they've chosen something. Even so, these are small things and I think the benefit of writing them this way are much greater (both from a performance and coding standpoint) than the hassle it would be to write it so that it's fully abstracted. I'd love to be proven wrong though! If there's an easy way to do this without tying it to MySQL specifically, please let me know. Yeah, that may be a disadvantage, but really, how often do you switch database types in the middle of a project? Database abstraction is a great selling point for tools like Propel, but I think the reality is that it’s highly unlikely that most people will ever switch a project over to a new database once they’ve chosen something. Even so, these are small things and I think the benefit of writing them this way are much greater (both from a performance and coding standpoint) than the hassle it would be to write it so that it’s fully abstracted. I’d love to be proven wrong though! If there’s an easy way to do this without tying it to MySQL specifically, please let me know.

]]> By: NiKo http://blog.mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-4 NiKo Wed, 12 Dec 2007 07:17:50 +0000 http://mirthlab.com/2007/12/11/custom-propel-criteria-tips/#comment-4 Cool but here you loose the advantage of database abstraction as these instructions are mysql specific. Anyway this can greatly help. Cool but here you loose the advantage of database abstraction as these instructions are mysql specific. Anyway this can greatly help.

]]>