db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Fischer <fisc...@seitenbau.net>
Subject RFC: Converting to Criteria / Criterion Interface.
Date Tue, 03 Jan 2006 16:55:49 GMT

Greg, the attachments did not make it to the mailing list. Can you create a
scarab issue instead, please ?



"Greg Monroe" <Greg.Monroe@DukeCE.com> schrieb am 03.01.2006 17:39:55:

> I had some time before Christmas break to do a quick first pass at
> taking all references to Criteria and Criterion in the Runtime classes
> to use a matching Interface class (boringly named CriteriaInterface
> and CriterionInterface).
> These interfaces are not based on just extracting all methods from
> current classes.  Instead they have been limited to the methods
> that are currently by the Runtime classes that use Criteria (e.g.
> BasePeer, SQLBuilder, and the like).
> The thought here is to allow for new Criteria and Criterion classes
> to be added without changing the existing ones.  IMHO, a good
> way to start looking at supporting things like functions and other
> things talked about without adding even more methods to the
> Criteria class.
> This work is at a stage that all dev's interested in Torque should get
> a peek at it and make comments.  So, I'm attaching the first pass at
> the interfaces to this.
> Some issues that I know still need to be done:
> The interface probably should be morphed into a clear design rather
> than a "it's there because someone used it in a class".
> Templates generate Criteria references.
> Template generated classes create Criteria classes in several places.
> There will need to be a Criteria "factory" methodolgy worked out to
> replace these.
> Greg
> <<CriterionInterface.java>> <<CriteriaInterface.java>>

> Greg Monroe    <Monroe@DukeCE.com>    (919)680-5050
> C&IS Solutions Team Lead
> Duke Corporate Education, Inc.
> 333 Liggett St.
> Durham, NC 27701
> Duke CE Privacy Statement
> Please be advised that this e-mail and any files transmitted with it
> are confidential communication or may otherwise be privileged or
> confidential and are intended solely for the individual or entity to
> whom they are addressed.  If you are not the intended recipient you
> may not rely on the contents of this email or any attachments, and
> we ask that you  please not read, copy or retransmit this
> communication, but reply to the sender and destroy the email, its
> contents, and all copies thereof immediately.  Any unauthorized
> dissemination, distribution or copying of this communication is
> strictly prohibited.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org

To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message