Databaseschema upgrade

Magnus_Salgo_(IDNordicAdmin_(Delete)_2300172)

Hi I have a version 1 module with a database schemaIn version 2 I would like to change the size of 3 fields and add 3 fields.What should I do to let Livelink upgrade the schema for me ...I have set the fVersion in ModuleDBOObjectI have _sql script ==> new installations works okWhat more to do and is it documented somewheremagnus@ids.se

Find more posts tagged with

Comments

Magnus_Salgo_(IDNordicAdmin_(Delete)_2300172)

Could some explain where this is documented or how to do it ???Regardsmagnus@ids.se

Jeff_Lang_(lang_(Delete)_2245920)

Magnus,Here are a couple of steps that should help you. Remember to look at existing code in the DBWizApi and WFMain ospaces for examples.1. Go to the ModuleDBObject object and update the fDBVersion. Also make sure that the fInstallScripts and fUninstallScripts features are still correct for the new schema. 2. Add a new child to the ExecPkg object in your ospace. If your fDBVersion went from {1,0,0} to {1,0,1} you would name the new child of ExecPkg Update1001. The script you want to change in your new child object is UpdateSchema. Look at the children of ExecPkg in DBWizApi or WFMain for examples of what the script should look like. The pkg parameter is the object that contains your SQL creation scripts. 3. Now go to the object that contains your SQL creation scripts and update them so that they create the new schema. Create new scripts using the naming convention upd1001_sql based on your new fDBVersion number. These new scripts are the ones that will be called from the UpdateSchema script in your new child of ExecPkg. These upd scripts contain the code to update the old schema to the new schema. Once again, look for examples in DBWizApi or WFMain. Once all this is done. Stop and restart the builder. When you try to log into the system via a web browser you will be told that your database schema is out of date and you need to upgrade your system. Go to admin.index and upgrade the database. If all your scripts are correct you should work.hope this helps,jeff

eLink User

Message from Bax Ruud, F.C. via eLinkL.s.I don't think this is what he means. When using multiple HTTP-serversinstalling a moduleis a bit tedious. Once you've installed the module on one HTTP-server the(shared) databaseis upgraded already (check the kini-table for version info on modules). Whentrying to upgradethe other one it starts complaining about upgrading the database.To install the second module you should directly enter the URL for theinstall-modules pagewhich should look something like this.http://owcsi001/livelink/livelink.exe?func=admin.installModuleKind regards,Ruud Bax> -----Oorspronkelijk bericht-----> Van: eLink Discussion: Development Discussion> [SMTP:development@elinkkc.opentext.com]> Verzonden: dinsdag 29 mei 2001 2:05> Aan: eLink Recipient> Onderwerp: Re Databaseschema upgrade of module> > Re Databaseschema upgrade of module> Posted by lang on 05/28/2001 09:01 PM> > Magnus,> > Here are a couple of steps that should help you. Remember to look at> existing code in the DBWizApi and WFMain ospaces for examples.> > 1. Go to the ModuleDBObject object and update the fDBVersion. Also make> sure that the fInstallScripts and fUninstallScripts features are still> correct for the new schema.> > 2. Add a new child to the ExecPkg object in your ospace. If your> fDBVersion went from {1,0,0} to {1,0,1} you would name the new child of> ExecPkg Update1001. The script you want to change in your new child object> is UpdateSchema. Look at the children of ExecPkg in DBWizApi or WFMain for> examples of what the script should look like. The pkg parameter is the> object that contains your SQL creation scripts.> > 3. Now go to the object that contains your SQL creation scripts and> update them so that they create the new schema. Create new scripts using> the naming convention upd1001_sql based on your new fDBVersion number.> These new scripts are the ones that will be called from the UpdateSchema> script in your new child of ExecPkg. These upd scripts contain the code to> update the old schema to the new schema. Once again, look for examples in> DBWizApi or WFMain.> > > Once all this is done. Stop and restart the builder. When you try to log> into the system via a web browser you will be told that your database> schema is out of date and you need to upgrade your system. Go to> admin.index and upgrade the database. If all your scripts are correct you> should work.> > > hope this helps,> jeff> > [To reply to this thread, use your normal e-mail reply function.]> > ============================================================> > Topic: Databaseschema upgrade> https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=252247> 6&objAction=view> > Discussion: Development Discussion> https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303> &objAction=view> > Livelink Server:> https://knowledge.opentext.com/knowledge/livelink.exe> > DISCLAIMERDit e-mail bericht is slechts bestemd voor de (rechts) persoon aan wie het is gericht, en kan informatie bevatten die persoonlijk of vertrouwelijk is. Deze informatie mag niet openbaar worden, tenzij hierom uitdrukkelijk in het e-mailbericht verzocht wordt, dan wel uitdrukkelijk door de verzender en ontvanger van het bericht overeengekomen is.Indien een ander dan de geadresseerde dit e-mail bericht ontvangt, anderszins in handen krijgt of redelijkerwijs kan vermoeden dat de in het bericht verzonden informatie niet voor hem of haar bestemd is, is hij of zij niet gerechtigd tot kennisneming, verspreiding, openbaar maken of vermenigvuldiging daarvan.Hij of zij wordt verzocht Ingenieursbureau ?Oranjewoud? B.V. onmiddellijk telefonisch op de hoogte te stellen en het e-mail bericht te vernietigen.Ingenieursbureau ?Oranjewoud? B.V. staat niet in voor de juiste, tijdige en volledige overbrenging van de inhoud van een verzonden e-mail bericht._______________________________________________________________________________________The information contained in this e-mail message is solely intended for the (legal) person to whom it has been sent. And as it may contain information of a personal or confidential nature, it may not be made public, unless this was specifically requested in the e-mail message, or specifically agreed upon by the sender and receiver of the e-mail message.If someone other than the intended recipient should receive or come into possession of this e-mail message, or can reasonably presume that the information contained in the e-mail message is not intended for him or her, he or she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to inform Ingenieursbureau ?Oranjewoud? B.V. immediately by telephone, and to destroy the original e-mail message.Ingenieursbureau ?Oranjewoud? B.V. does not accept any liability for the correct, timely and complete transmission of the contents of a transmitted e-mail message.

Magnus_Salgo_(IDNordicAdmin_(Delete)_2300172)

Thanks Jeff it seems to work Small question 1: When I do a new installation it seems that I have to go to the upgrade database.Before I added the update scripts it was installed directlyHave I done anything wrong ?Small question 2: The naming standard if you go from 1.0.0 to 2.0.0 what should the update script be called does it matter ?!?!?Thanks again I found the DBWizApi examples and they helped...Magnus SalgoStockholmSwedenPs. Jeff hope that you will have some session on next LivelinkUp in Las Vegas ...You are more than welcome to Europe maybe for a partner update of next version ....

Jeff_Lang_(lang_(Delete)_2245920)

Magnus,To answer question 1 you should make sure that at the bottom of your install SQL script you have the following:insert into %Prefix%KIni values( '%IniSection%', '%IniKeyword%', '{8,0,2}' )where the '{8,0,2}' is replaced with the .fDBVersion feature in your ModuleDBObject. That should keep the upgrade from having to happen.The answer for question 2 is that the script should be called upd2000_sql. I'm not sure if it matters, but that is the convention.I'll probably be in Vegas doing something this year, I'm not sure what it will be yet. I'm on vacation in Australia and I've been here since February so I haven't written a ton of stuff for the new release, but I think I'll have a bag of goodies for workflow and forms to demo at the conference. I'm keeping up with what's going on at work from our offices here and meeting our Aussie team. Maybe next time I'll get to Europe and see all the people there.jeff