| Key: |
XPR-120
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
Billy McCafferty
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
xplanner
Created: 29/Sep/05 10:57 AM
Updated: 30/Nov/05 02:23 AM
|
|
| Component/s: |
Installation
|
| Affects Version/s: |
0.7
|
| Fix Version/s: |
0.7
|
|
| JDK version and platform: |
1.5 for Windows
|
| Database: |
MySql 1.4
|
| Application server: |
Tomcat 5.5
|
|
I had trouble upgrading the install of 0.602 DB using the SQL scripts that came with the installation package. There were a number of issues including placing primary keys when they already existed and attempting to drop columns that didn't exist. The attached SQL script has a number of lines prefixed by /* CUSTOM LINE */. The immediately following line are lines that I modified to make the script work. My original 0.602 was originally a fresh install...it was not an upgrade from a previous version. I only needed to change the "A" script...the "B" script worked fine.
|
|
Description
|
I had trouble upgrading the install of 0.602 DB using the SQL scripts that came with the installation package. There were a number of issues including placing primary keys when they already existed and attempting to drop columns that didn't exist. The attached SQL script has a number of lines prefixed by /* CUSTOM LINE */. The immediately following line are lines that I modified to make the script work. My original 0.602 was originally a fresh install...it was not an upgrade from a previous version. I only needed to change the "A" script...the "B" script worked fine. |
Show » |
|
There were problems with the upgrade script from 0.602 to 0.7b1 (fix attached)
