nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Update Schema through Module

General_Dynamics_IT

Hello,I build an Ospace that needs to upgrade the schema by adding a table with a couple of fields. Module installs, and recieve a page that states the Database needs to be upgraded before going forware.Going to the Admin.index page and going to Maintain Database > Upgrade Database states that the "new" module is installed and the Schema will be upgraded to it's version. After selecting "Upgrade Database", I get the "[Mon Apr 28 11:23:36 2003] : [Mon Apr 28 11:23:36 2003] : Database upgrade started" message the is supposed to refresh, which it does. Unfortunately that's all it does, it never updates the schema and I have to manually uninstall the module to get Livelink working again.I'm using LL 9.1 SP2 with Oracle 8.1.7 on Win 2K server, I've followed the instructions in the Livelink Module Developers Guide and looked at the "Polling", "IDTLearning", "Forms"...ospaces to see what I am doing wrong but I can't find anything.Any help appreciated.Thanks,Mike

Find more posts tagged with

Comments

General_Dynamics_IT

Part of the problem was that the feature Oracle had a value of '#5e000109' but wasn't actually pointing to the "DBScripts>Oracle" Child Node. I eventually deleted the Oracle feature opened up a second Ospace Browse window and dragged the Oracle Child to the DBScripts node and added the feature that way.One area of confusion: How do you override a feature that is inherited with the value of a Node (ie. #1234567)? I'm trying to override the fScripts value with the value of the DBScripts Node but it won't let me. The only way I can change the value is if I make it a String instead of a Dynamic. If I do that and then Inspect the fScripts feature, it doesn't bring me to the DBScripts child object.Did I confuse you?

)Any help appreciated.Mike

Howard_Pell

Message from Howard Pell <<A HREF="mailto:hlpell@opentext.com">hlpell@opentext.com> via eLink

eLink

I amslightly confused. ;-)

You shouldhave no problem overriding fScripts even if it is inherited. Where you wouldrun into trouble is if you tried to override something like OSParent which mustpoint to its parent. As for making fScripts a string, that won’t work as youhave already found out. It must be dynamic (actually it is a reference butnever mind). FScripts must remain as a dynamic as it was when you made theorphan of ModuleDBObject.

<![if !supportEmptyParas]> <![endif]>

Might I suggestyou delete the orphan of ModuleDBObject and begin again? Now edit (doubleclick) fScripts and edit the hexadecimal number to the number of the DBScriptsobject. If this still doesn’t work then you could zip your module and email itto me. I’m in the classroom all week but will try to look at it as soon as I can.

<![if !supportEmptyParas]> <![endif]>

Howard

<![if !supportEmptyParas]> <![endif]>

______________________

Howard Pell

Senior Technical Educator

Liaison, Special Projects

Open Text Corporation

www.opentext.com

(1-519) 888-7111 Ext. 2203

<![if !supportEmptyParas]> <![endif]>

-----OriginalMessage-----
From: eLink Discussion:Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: Monday, April 28, 2003 3:29PM
To: eLink Recipient
Subject: Part of the Problem

<![if !supportEmptyParas]> <![endif]>

Part of the Problem		Posted by GenDUser6 (Network Systems, General Dynamics) on 04/28/2003 03:18 PM
In reply to: Update Schema through Module		Posted by GenDUser6 (Network Systems, General Dynamics) on 04/28/2003 01:38 PM

<![if !supportEmptyParas]> <![endif]>

Part of the problem was that the feature Oracle had a value of '#5e000109' but wasn't actually pointing to the "DBScripts>Oracle" Child Node. I eventually deleted the Oracle feature opened up a second Ospace Browse window and dragged the Oracle Child to the DBScripts node and added the feature that way.

One area of confusion: How do you override a feature that is inherited with the value of a Node (ie. #1234567)? I'm trying to override the fScripts value with the value of the DBScripts Node but it won't let me. The only way I can change the value is if I make it a String instead of a Dynamic. If I do that and then Inspect the fScripts feature, it doesn't bring me to the DBScripts child object.

Did I confuse you? )

Any help appreciated.
Mike

General_Dynamics_IT

Hi Howard,Thanks for the quick response. I did try from scratch and this is what I get when I try to override the fScripts (or fExecPkg) with a hex number. "#d (unknown)" in the browser status bar at the bottom. If I then edit the feature I see a #d as the dynamic content. For some reason it's not keeping the hex number that I gave it #a500011f.I'll zip up the Ospace and send it to you. Thanks for the help.In the mean time I'll try to start from scratch again with the ModuleDBObject.Thanks!!Mike

Magnus_Salgo_(IDNordicAdmin_(Delete)_2300172)

Open Text I think Hans Stoop has done a Livelink module where some steps are done by a menu option like adding a db schema --> you will not do any mistakes...Developing with that makes life in Ospace a lot of easier ...Regardssalgo@ids.se

Mike_Oliver_(INMUser1_(Delete)_2518941)

We also have a module that has a Wizard for creating a new module with many options like new node types and request handlers plus oscript prototyping and the ability to use a web browser to access internal Livelink Objects, inspect features, etc.

Magnus_Salgo_(IDNordicAdmin_(Delete)_2300172)

Does it support multi development environment?!?!Will you be in Paris on Livelink UpRegardsMagnus S?lg?

Desmond_Yeung_(dowuser1_-_(deleted))

We have similar problem. When the hex number is "too big", say "#9500010e", the dynamic features will not accept it. Do you get any reply from OTC? Could you share with me how you solve this problem? Thanks.

General_Dynamics_IT

I did not get any response from OT because we do not have Builder Support. There were a couple of people that were looking into it in their own time but I didn't get an answer to my issue.The only way I could get around it was to drag the ExecPkg to the DBObject and name it fExecPkg2. (It won't allow you to name it fExecPkg because it already exists) Then I renamed fExecPkg2 to fExecPkg. It now shows 2 entries in the features list of DBObject named (O)fExecPkg and (N)fExecPkg.Hope this helps.