Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#13 2009-11-27 04:55:06

artagesw
Member
From: Seattle, WA
Registered: 2007-04-29
Posts: 227
Website

Re: An idea for Txp 5, regarding db abstraction and more

The existence of PDO in PHP5 is one of the many factors behind the decision to make PHP5 a new base requirement in Txp 5.

Offline

#14 2009-11-29 17:08:17

Mary
Sock Enthusiast
Registered: 2004-06-27
Posts: 6,236

Re: An idea for Txp 5, regarding db abstraction and more

I’ve looked at the other PHP ORM (other than Propel) I could find. There’s lots of projects, but in my opinion, not much competition (but correct me if my evaluation is wrong). Almost all of the ones I could find are not yet contenders, though they could become great projects eventually.

  • ADOdb has a simple ORM within it. However, it does not use PDO, and it is comparable in size to Doctrine, yet doesn’t have things such as Doctrine’s Behaviors, Utilities, data validation, etc.
  • PHP ActiveRecord: Looks promising, though it is quite young in it’s development and there’s little documentation thus far. Something to watch, for those interested in a light-weight ORM.
  • phpDataMapper: Extremely young, unstable/under heavy development, little documentation. However it is also something to watch.
  • dORM: Also quite young (and unstable?), little documentation, and uses XML config files (yuck).
  • Repose: Extremely young and unfinished, no documentation.
  • Outlet: Young, little documentation.
  • RedBean: Has some weird terminology unique to itself, odd way of defining table relationships, little documentation.
  • Porte: Young, no new releases in a while, little documentation.
  • EZPDO: No new releases in some time. Code is inside comments?? What?
  • PHPLinq: Pretty young, no documentation
  • CoughPHP: No new releases in a while. Very little documentation.
  • ORMer: Young, no releases, cannot even access the repo, no documentation.
  • Pork.dbObject: Just some examples, no documentation.
  • Hormon: Not even released yet, no documentation.

Are there any others I have missed?

So, if an ORM is a go for Txp, Doctrine would definitely be my vote. Otherwise, I’d just be keen on the move to PDO alone.

Last edited by Mary (2009-11-29 17:08:49)

Offline

#15 2009-12-18 18:47:33

wet
Developer Emeritus
From: Schoerfling, Austria
Registered: 2005-06-06
Posts: 3,330
Website Mastodon

Re: An idea for Txp 5, regarding db abstraction and more

Doctrine vs. Propel. Seems like there’s a preference evolving.

Offline

Board footer

Powered by FluxBB