We recently got into a situation where we were able to get a few new
portlets, a new layout user, and new fragment working in one
environment's DB, but not in the target environment's DB, and it is a
mess to diff these (even with table exclusions, etc.) because layout
user data is mixed up with other user data and their changes to
user-specific layouts and preferences in the schemas. This is DLM but a
much older version of uPortal, and the issue we are having is not
something that would typically be a problem for most, but I've started
to wonder whether this data is better separated in uPortal 3.3?
I understand that schema changes are not to be taken lightly, as the
ease of upgrade and speed and efficiency of DB operations are much more
important. But, maybe if user and group layout data are still entwined
in uP 3.3, is there any chance that group layout/fragment data and user
layout data is at least maybe a little easier to follow in the latest
uPortal? If not, could schema changes to make it easier to manually
restore group layout/fragment data be considered specifically for a
future major release if it didn't significantly affect performance?
Really sorry if this sounds lame.
Thanks,
Gary
--
You are currently subscribed to uportal-dev@lists.ja-sig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
