I pushed to get this added back into the User interface, but could not
convince Rafal. And I am starting to change my mind. For example in
Flux, I believe it is possible to change a user's username. This
functionality may not be appropriate if authorization information is in
LDAP storage, as this may be the only info available to determine a
user. It is probably better then that if Flux makes the decision to
allow username changes, then it be explicit about the type of User
implementation it expects.
If User.getPrimaryKey() key exists alongside User.getUserName() then an
application like Flux could allow changes to one property while assuming
the other invariant, when some User implementations may only have one
unique piece of information. If an app uses the User interface,
designers may overlook the fact that they are designing in
implementation specific functionality, if the interface contains
convenience methods geared towards one (very important) implementation.
So, I am beginning to see Rafal's point, and it is going to be up to
others to convince Rafal otherwise.
John McNally
Steve Ruby wrote:
>
> > >
> > > You now need to do a cast because Rafal thinks that an ID for a user
> > should
> > > be deprecated (however, it makes sense from the standpoint of using a
> > > relational db and needing to do associations...thus, you have to do a
> > nasty
> > > cast...i hate casting).
> > >
> > > ((TurbineUser) data.getUser()).getIdAsInt()
> > >
> > > -jon
> > >
>
> As a lowly user I would have to say, "Please keep user id," I'm finding
> this in the archives because I'm finding out that my beloved data.getUser().getID()
> is gone :(. For the exact reason Jon mentions a very user-centric application
> with many tables using TURBINE_USER as the base user information we don't
> want to have to relate off of the UserName, and waste many characters of space.
>
> What is the arguement for droping the userID (other than the fact that
> there are two uniqe keys on TURBINE_USER table)?
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
