You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Scott T Weaver (JIRA)" <je...@portals.apache.org> on 2006/01/06 16:33:16 UTC
[jira] Created: (JS2-463) Database Upgrade scripts
Database Upgrade scripts
------------------------
Key: JS2-463
URL: http://issues.apache.org/jira/browse/JS2-463
Project: Jetspeed 2
Type: Improvement
Components: Deployment, Installer, Project Build
Versions: 2.1-dev, 2.0-FINAL
Reporter: Scott T Weaver
Priority: Critical
Moving to the release version of Jetspeed 2, I have run into enough database changes to make upgrade fairly painful.
1. The format of the PREFS_PROPERTY_VALUE was completely altered requiring manual migration of existing data from the old table format to the new (see the attached .sql file for example script to move existing prefs).
2. The page statics system was added, not a big deal, but still was suprise and required digging into the logs to locate the issue.
The issue is that on existing build systems I cannot simply wipe/recreate the database like I do on a local dev system and now that we have a release and will try to release incremental builds we should really focus on migration and upgrade scripts for the database.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-463) Database Upgrade scripts
Posted by "Scott T Weaver (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-463?page=all ]
Scott T Weaver updated JS2-463:
-------------------------------
Attachment: migrate.sql
Migration script (MSSQL Specific)
> Database Upgrade scripts
> ------------------------
>
> Key: JS2-463
> URL: http://issues.apache.org/jira/browse/JS2-463
> Project: Jetspeed 2
> Type: Improvement
> Components: Deployment, Installer, Project Build
> Versions: 2.1-dev, 2.0-FINAL
> Reporter: Scott T Weaver
> Priority: Critical
> Attachments: migrate.sql
>
> Moving to the release version of Jetspeed 2, I have run into enough database changes to make upgrade fairly painful.
> 1. The format of the PREFS_PROPERTY_VALUE was completely altered requiring manual migration of existing data from the old table format to the new (see the attached .sql file for example script to move existing prefs).
> 2. The page statics system was added, not a big deal, but still was suprise and required digging into the logs to locate the issue.
> The issue is that on existing build systems I cannot simply wipe/recreate the database like I do on a local dev system and now that we have a release and will try to release incremental builds we should really focus on migration and upgrade scripts for the database.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Closed: (JS2-463) Database Upgrade scripts
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-463?page=all ]
Ate Douma closed JS2-463.
-------------------------
Resolution: Won't Fix
This migration script is outdated as well as MSSQL specific.
For the 2.1 release, we'll need proper migration support, but probably not this way.
> Database Upgrade scripts
> ------------------------
>
> Key: JS2-463
> URL: http://issues.apache.org/jira/browse/JS2-463
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Deployment, Installer, Project Build
> Affects Versions: 2.1-dev, 2.0-FINAL
> Reporter: Scott T Weaver
> Priority: Critical
> Attachments: migrate.sql
>
>
> Moving to the release version of Jetspeed 2, I have run into enough database changes to make upgrade fairly painful.
> 1. The format of the PREFS_PROPERTY_VALUE was completely altered requiring manual migration of existing data from the old table format to the new (see the attached .sql file for example script to move existing prefs).
> 2. The page statics system was added, not a big deal, but still was suprise and required digging into the logs to locate the issue.
> The issue is that on existing build systems I cannot simply wipe/recreate the database like I do on a local dev system and now that we have a release and will try to release incremental builds we should really focus on migration and upgrade scripts for the database.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org