Printing the name of the enum should be done, I agree.
I was thinking updating the enum code to check for a custom/advanced
cayenne enum in addition to the current enum support. That way you
could support basic enums (the current approach) or more advanced
enums, where you need to control the values stored in the database.
/dev/mrg
On Jan 16, 2008 11:47 AM, Andrus Adamchik <andru..bjectstyle.org> wrote:
> As far as logging is concerned, IMO just indicating that a parameter
> is an enum and printing its name should be a good generic solution.
>
> Beyond logging ... I don't know... I'd like to discuss any ideas that
> do not require replacing a core java enum concept with a custom enum
> implementation.
>
> Andrus
>
>
>
> On Jan 16, 2008, at 6:38 PM, Michael Gentry wrote:
>
> > We can change this, but see my previous message to Kevin. Perhaps I
> > should work on more advances enumeration support?
> >
> > /dev/mrg
> >
> >
> > On Jan 16, 2008 11:04 AM, Andrus Adamchik (JIRA) <de..ayenne.apache.org
> > > wrote:
> >> Enum logging in SQL logs
> >> ------------------------
> >>
> >> Key: CAY-964
> >> URL: https://issues.apache.org/cayenne/browse/CAY-964
> >> Project: Cayenne
> >> Issue Type: Improvement
> >> Components: Cayenne Core Library
> >> Affects Versions: 3.0
> >> Reporter: Andrus Adamchik
> >> Assignee: Andrus Adamchik
> >> Priority: Trivial
> >> Fix For: 3.0
> >>
> >>
> >> Currently SQL logs generated for enum bindings look pretty ugly. E.g.
> >>
> >> [bind: 1:'%a%', 2:'%b%', 3:30, 4:com.example.MyEnu..3714924]
> >>
> >> Need to log enum name instead
> >>
> >>
> >> --
> >> This message is automatically generated by JIRA.
> >> -
> >> You can reply to this email to add a comment to the issue online.
> >>
> >>
> >
>
>
This archive was generated by hypermail 2.0.0 : Wed Jan 16 2008 - 11:54:07 EST