Forum OpenACS Development: Best way to handle add'l user info?
There is some data that is not in the user model for OACS4.
PhilG's site seems to indicate that the creation of a
"users_extra_info" table is the way to go. Then make a primary key
constraint against the users table and unique index constraint to
ensure that no key is entered twice.
Is this the best way to go about it, or is there something already in
OACS4 that lets me add more information to the user information?
It's possible that in the future upgrades won't be as painful as they have been in the past, and this will become bad advice, but I think upgrading software like this is always pretty hard. What we have done so far is start with a clean install of the new version and migrate over all our changes; if you're careful to document them well then it's not all that hard to do.