$InstDir\*.sql missing in 6.4.1

Known bugs reported by PacsOne users
Post Reply
tburba
Posts:50
Joined:Fri Apr 23, 2010 5:02 pm
Contact:
$InstDir\*.sql missing in 6.4.1

Post by tburba » Fri May 23, 2014 1:33 am

6.3.8 installs db_schema.sql and upgrade_schema.sql but 6.4.1 doesn't. Their contents were moved to Setup.exe.

Is there some other reason besides programming convenience? If not, then Setup.exe should just create them anew. It's not difficult to "play back" those strings to a file as well. Currently they are not particularly human readable but that's no problem for mysql.exe.

Absence of those files became a big surprise to me. I was planning a PACS upgrade which involves new hardware, new version of MySQL and, of course, PacsOne. The logical scenario is to make a copy of the old database, run upgrade_schema.sql on it, make a dump that includes only data, then import into the database of the new PACS. Eventually I managed all those steps except the last one, as the new installation is still in trial mode and will complain about exceeded limits.

Now the second part due to which I placed this under Known Bugs instead of Desired Features.

After executing the current equivalent of upgrade_schema.sql on a database from 6.1.2, the resulting database schema is different compared to a fresh installation of 6.4.1:

1) table "groupmember" is present in the fresh database but not in upgraded one;

2) table "hl7observation" is absent in the fresh database but remains after upgrade;

3) "hl7*phone.phonenumber" are 40 characters in the fresh database but 64 in the upgraded one;

4) "hl7job.retries" is 3 characters in the fresh database but 4 in the upgraded one;

5) a few tables have a different column order.

I don't know how much important this is (for example, #5 is not critical if all your statements include column names), however you might want to check both sets of queries more thoroughly.

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Fri May 23, 2014 3:09 pm

Starting from version 6.4.1 of PacsOne Server, the database schema files are no longer included with the installation packages as they have now been integrated into the Installer (Setup.exe).

The proper method for upgrading an existing PacsOne Server installation is to follow the step-by-step instructions detailed in the "Upgrade" section of the PacsOne Server Installation Guide (http://www.rainbowfishsoftware.com/install.pdf), instead of playing with the database schema files because upgrading the database schema is merely one part of the upgrade process.

tburba
Posts:50
Joined:Fri Apr 23, 2010 5:02 pm
Contact:

Post by tburba » Fri May 23, 2014 5:12 pm

Well, in my case the installation is brand new (new hardware, new Apache/MySQL/PHP, new PacsOne) and I just need to initialize the database with contents of the old one. A license transfer is involved so everything is legal.

Looks like I will need to stop the PacsOne service, initialize the database from a dump (because MySQL does not accept older binary files), then use Setup.exe for the upgrade (no problem as we purchased the upgrade password as well).

Temporarily using old versions of Apache/MySQL/PHP on the new hardware means more work, which I want to avoid.

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Tue May 27, 2014 3:04 pm

Yes, you should run the Installer (Setup.exe) along with a valid upgrade password to upgrade your existing database to the latest version of PacsOne Server.

Post Reply