Yeah, your example works in all combinations of M3/trunk and Extended
enum vs. Java enum... I guess there was some other thing in my project
(that I since remapped as String) that made it blow... I can think of
two things - relationships and inheritance. I am pretty sure
inheritance wasn't involved. So it was probably an issue similar to
this:
https://issues.apache.org/cayenne/browse/CAY-1034
I guess we can close CAY-1014 and see if we can improve relationship
validation...
Andrus
On Apr 24, 2008, at 4:35 PM, Michael Gentry wrote:
Hmm, I used the ExtendedEnumerations which aren't in M3. When I
changed my State class to look like:
public enum State
{
AL, AK, AR, AZ, DC, MD, TN, VA;
}
It still worked with M3.
On Thu, Apr 24, 2008 at 9:22 AM, Michael Gentry
<[EMAIL PROTECTED]> wrote:
Sorry, already sent the attachment. Nothing sensitive in it, though
(custom test db/table).
Let me see if I have M3 lying around and I'll try it.
/dev/mrg
On Thu, Apr 24, 2008 at 9:19 AM, Andrus Adamchik <[EMAIL PROTECTED]
> wrote:
Sure, or you can attach it to CAY-1014 if you don't have any
sensitive info
in it.
Wonder if my related fix had any effect on this? Could you try it
with M3
if possible?
Thanks,
Andrus
On Apr 24, 2008, at 4:16 PM, Michael Gentry wrote:
Andrus, I'm going to send you a test I just did via e-mail since
the
list doesn't support attachments. Enums as PKs worked for me.
What
issue were you seeing?
Thanks,
/dev/mrg
