Login | Register
My pages Projects Community openCollabNet

Reply to message

2020-03-13: This site is going to be decommissioned and shut down very soon. Please copy and archive any data you wish to keep ASAP

* = Required fields
* Subject
* Body
Send reply to
Author (directly in email)
Please type the letters in the image above.

Original message

Author Alan Pinstein <apinstein@mac.com>
Full name Alan Pinstein <apinstein@mac.com>
Date 2006-05-29 09:03:50 PDT
Message Thanks for kicking this off.

I posted something about a year ago (I can't believe I've been using
Propel for a year!) and I think most of the comments are still relevant:


You've got a good start, but as you've mentioned, Criteria is
currently good at simple things but not a complex ones. Yet your
examples on the planning page are still relatively simply queries.

I think we should think about the interface for the more complicated
parts as well:

1) Joining and table aliasing
2) Sorting and pagination

Can you explain the Query* classes more?

I'd be happy to contribute time to flushing out design over the next
few weeks.



On May 26, 2006, at 2:37 PM, Hans Lellelid wrote:

> Hi -
> I put together a rough proposal/strategy for a new Criteria API on the
> wiki page.
> http://propel.phpdb.​org/trac/wiki/Develo​pment/Criteria
> The implementation is still only very loosely conceptual and it
> doesn't
> address all the functionality of the current system yet. It does,
> however, provide a more consistent & somewhat more intuitive system
> (both to use & to develop, in my opinion). The design is based
> loosely
> on the Hibernate Criteria API and the way that the logical expressions
> are handled by Phing's Condition system.
> I think it's a good starting point, and would be interested in any
> comments at this point.
> Hans
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org