> I want to have the group aliases controlled in an alias database table,
> just like JDBCVirtualUserTable. I don't want to have to update the
> config every time I add another group alias. Do the changes you plan on
> for the Redirect stuff involve functionality like that?
When I am finished, Redirect will have some additional functionality, and
will be the basis for all mailets that have redirect/forwarding behavior,
which is what Danny intended in the first place. Right now there are a few
things that prevent JDBCVirtualUserTable from being a sub-class of Redirect,
and those would be changed. And all of the other mailets rewritten to
subclass Redirect as well.
> I really like JDBCVirtualUserTable, the only thing it's missing for my
> need is a one to many relationship between aliases.
Yes, I understood. :-) My primary concern is how the SQL query is used to
implement the mapping, but I'll play with it. As you noted, the issue is
coming up with "a good database design that allows [mulitple rows to
represent] the 1:n relationship and still support the single select that
falls back to a catch-all alias."
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
