Bruce Snyder wrote:
I believe that this is bug in the alias creation so I've filed a Bugzilla report on it:
http://bugzilla.exolab.org/show_bug.cgi?id=1483
Many thanks for that.
I think it's a pretty simple thing to fix. The reason that it hasn't been fixed yet is that this type of alias is only created for a use case where classes of the same type are being joined (aka self-join). Castor does not directly support self-joins, but there's a slight chance that it might work for you.
I'm new to Castor JDO and how it works. Is there a better idiom for doing this kind of thing that I should use?
Anyway I am generating a test case for this situation and I'd like to get your client code from you to include in the test. Please post it to the mailing list so that I can proceed.
My client code wouldn't make a good test case. I'll spend a little time this evening extracting a simple case and post that here. Do you just need source code or mapping file, sql schema, sample data, etc.. as well?
I also had a brief look at the Castor source to try and understand what is happening. It's a bit overwhelming but HSqlQueryExpression.java seems to be where the action is. Am I on the right track?
Regards,
Matt
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
