So what's the solution here then, it's a hard fix because people already use it right?
Might have to do the slow deprecation process.
Travis
---- Original Message ----
From: Eric Dobbs <[EMAIL PROTECTED]>
Sent: 2002-04-25
To: [EMAIL PROTECTED]
Subject: Why I don't like Criteria (was Re: Crossdb and Criteria Patch)
On Thursday, April 25, 2002, at 05:42 PM, Sam Joseph wrote:
> Is there some simple summary somewhere of what else you think is wrong
> with Criteria and why it needs replacing?
I don't think there's a good summary but here's
a few off the top of my head:
1. wish it didn't extend hashtable,
would prefer 'has-a' instead of 'is-a'
2. wish it wasn't implemented as a hashtable at all,
the use of column names for keys means
"FOO >= 10 AND FOO < 20" must use a Criterion.
3. Criterion is ugly, and I wish client code didn't even know
about it.
4. as you have pointed out, queries of modest complexity using
nested Criterion have precedence problems (which is why I'm
interested in your patch).
5. it's an essential piece of Torque's API -- client code
everywhere will be effected by corrections to the above
problems making it hard to fix 1-4
-Eric
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
