ClearHealth: ClearHealth => SQL Upgrade to 2.2

Members

Help

Home

Home » ClearHealth Forums » ClearHealth » SQL Upgrade to 2.2

Show: Today's Messages :: Show Polls :: Message Navigator

SQL Upgrade to 2.2 [message #3053]

Sat, 03 May 2008 20:35

jmax
Messages: 600
Registered: March 2007
Location: MA

After many days of dissecting the changes I am almost at the very end of the tunnel and the light looks bright.
I have one final question.
I am trying to migrate the enumeration and enumeration_definition tables now - the final ones.
In CH 1.x default schema the enumeration_definition.enumeration_id started from 300466 and ended around 812288 and had 47 rows.
The 2.2 version now has values staring from 1 to 102 (without gaps and much cleaner) and has 102 values.

My question is what should I do - if I overwrite my 1.x table with the 2.2 table - what repercussions does it have on my existing data.

I am assuming I must have used the enumeration_id somewhere else to reference something as I used CH over the years.
Should I overwrite, I am kind of lost here.
I also want to know the relation between this and the enumeration_value table and have the same upgrade question on it.
I am "this close" and need some help to cross the finish line.
I will post my DDL and DML scripts for others as soon as I am done without errors.

Thanks in advance.

Report message to a moderator

Re: SQL Upgrade to 2.2 [message #3060 is a reply to message #3053 ]

Tue, 06 May 2008 00:27

jay.walker
Messages: 961
Registered: January 2008
Location: Tucson AZ

You will want to use your old enumeration tables. The key cleanup was done in preparation for our new enum live update tools. You will just want to determine any enums you may need to add in, it should be fine to add those one with the lower keys.

So I would recommend you:

*Wipe the enumeration_definition and enumeration_value tables in the 2.x install you are moving to
*Copy your old enums over to the new database

At runtime any missing enums will generate visible errors so just add those in as needed. On the adds use the sql from the 2.x series.

As far as I know nothing in CH aside from possibly some reports uses enum ids directly so having different ones shouldn't cause you any real problems.

-Jay Walker
Customer Service
ClearHealth Inc.

Report message to a moderator

Previous Topic:	2.2 fbclamiline schema changes revert again?
Next Topic:	CHMobile for the iPhone Released!

Goto Forum:

-=] Back to Top [=-

[ Generate printable PDF ] [ Syndicate this forum (XML) ] [

]

Current Time: Mon Sep 6 12:26:05 EDT 2010

Total time taken to generate the page: 0.01476 seconds

.:: Contact :: Home ::.