Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
In-Reply-To: <437120E9.9020302@backstagetech.com.au>
Subject: TRQS321: Criteria Serialization (was:Re: [VOTE] release Torque
 3.2-rc3 now)
To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Message-ID: 
 <OF178823FC.C19F797D-ONC12570B4.00303178-C12570B4.003952B5@seitenbau.net>
From: Thomas Fischer <fischer@seitenbau.net>
Date: Wed, 9 Nov 2005 11:25:51 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII


Scott,

I took a quick glance at the issue, and when I uncommented the test case
you checked in and resolved an issue of visibility (use
"Criteria.getNewCriterion()" instead of "new Criteria.Criterion"), the test
case did not produce an error.
Then I looked what the test case does, and it uses Criteria.equals(Object)
to test whether the two criteria are equal. This is not enough, since
Criteria.equals does not compare aliases and asColumns. There are two
possibilities to remedy this:
- The first is to change criteria.equals, which I did not want to do
between release candidates, but if somebody else is of another opinion
here,  we need to discuss it.
- the second one is to write a custom comparison for the test case and
remove it once Criteria.equals() is fixed. I admit I was too lazy to do it.

So the question is how we should proceed. If you wish, I can check in the
modified test case which runs for me, and then we can check whether it runs
for you also.
Then, I'm going to look at the old mails where the problem is described and
see whether I can reproduce it. Maybe the problem has dissolved into thin
air ??? (it is time for another miracle :-) )

I'll email if I find out anything new.

     Thomas

Scott Eade <seade@backstagetech.com.au> schrieb am 08.11.2005 23:04:25:

> I'd quite like to see http://issues.apache.org/scarab/issues/id/TRQS321
> resolved for 3.2 final, but it has been broken for a long time now and I
> can't guarantee that I will be able to pull enough time together to look
> at it.  If I can't get my act together in the next few days then we
> should go ahead without it.
>
> Scott
>


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