Development

ReplacingPropelWithEZPDO (diff)

You must first sign up to be able to contribute.

Changes between Version 5 and Version 6 of ReplacingPropelWithEZPDO

Show
Ignore:
Author:
mabs29 (IP: 83.146.13.125)
Timestamp:
02/14/06 20:08:52 (12 years ago)
Comment:

Supplemental comments to 'Maturity' disadvantage for ezPDO vs Propel.

Legend:

Unmodified
Added
Removed
Modified
  • ReplacingPropelWithEZPDO

    v5 v6  
    2525'''PDO Compatibility''': At the time of writing, ezPDO's support for PDO is in beta and included with the latest release. You are welcome to play with it, but it is recommended that you use ADODB or ADODB_Lite for your ezPDO installation until they have ironed out all the problems with their PDO implementation. 
    2626 
    27 '''Maturity''': While both Propel and ezPDO deal with M:N relationships, the more explicit approach by Propel may lead you to the conclusion that it is the more mature of the two. In the end, Propel boasts more features with less hassle. You deal with objects directly and if you need to make a transaction, you can create a special case of it whereas going through ezPDO manager makes transactions more natural
     27'''Maturity''': While both Propel and ezPDO deal with M:N relationships, the more explicit approach by Propel may lead you to the conclusion that it is the more mature of the two. In the end, Propel boasts more features with less hassle. You deal with objects directly and if you need to make a transaction, you can create a special case of it. ezPDO's transactional support is still shaky because it does not yet allow you to specify, for MySQL particularly, the table type (it defaults to MyISAM). So, foreign keys, indexes, etc. are either not supported or emulated through additional tables and therefore additional queries
    2828 
    2929'''Not integrated into Symfony''': This is the primary reason you may be encouraged to drop ezPDO. You must get the epManager instance each time you want to access your database and this pollutes your application with unnecessary clutter. Later in this wiki, we describe a way to make ezPDO a little more integrated.