>Unless I do misunderstand the matter, I have only two choices for about
>99% of my persistant classes:


i must agree most of my objects have only flieds which can be changed or
are not unique.

example a user has a login (email address) and a password both fields
should be changable. do i need to ask the user to give a extra unique
string so i can keep my objects apart?


would it be an idea to add my own id on object creation time.
this way i have a unique key which never is empty and don't need to
change. only problem is when objects get created in different vm's.