O$ - DAM issue - differences between dev and runtime

Phil Potter phil at pgpotter.demon.co.uk
Tue Apr 7 10:11:40 EDT 2009

Hi David,

did you try "Do Inherited" without the $ ?

As for errors, create a $sqlerror method within the table, which is 
called when you get a SQL error.

Although personally I'd have a table superclass with this $sqlerror 
method within it, so that you only need it in one place for all the 
tables you may create.


In article 
<82295ABB-AEDC-4902-B60F-7949836093C8 at charlie.housing.admin.nyu.edu>, 
David Walton <omuser at charlie.housing.admin.nyu.edu> writes
>Hi again,
>This do $inherited doesn't work - nor does do $inherited.$update
>Do default does work, but does not return an understandable value.
>Which begs another question: If you use a table class to override the 
>standard table $update() method, how would you check for sql errors?
>For now, I'm using a check to see whether $cinst.$rowsaffected is 
>greater than zero.
>On Apr 7, 2009, at 8:46 AM, Steve Finger wrote:
>> Hi,
>> Now I'm confused. In my table classes I override $update all the 
>>time and at the end put
>> Do default Returns %flag
>> %flag is a local variable and it returns 1 if successful and 0 if not
>> In my only experience with Oracle and SQL Server the Do default works 
>>the same with the 0 or 1 result.
>> I think (but I'm going from memory) there may have been a time it 
>>returned null from an sql statement that ended up being totally 
>>messed up and I guess the Dam didn't know what to do with it.
>> Steve Finger
>> Bastiaan Olij wrote:
>>> Hi David,
>>> As you are overrriding $update, do default is not the correct way to
>>> invoke the standard logic.
>>> Try either doing a "do inherited" or what I find easier/better 
>>> do $inherited.$update() returns lvSuccess
>>> Which allows you to parse any additional parameters.
>>> I can't remember off the top of my head when you had to use do 
>>> I hardly use that one in my code.
>>> Greetz,
>>> Bas
>>> David Walton wrote:
>>>> Okay... no responses. Let's try again.
>>>> I have a table method that is called $update. It processes some
>>>> history, checks that the user has changed some values, then says 
>>>> default" with a return value. The problem is that I get different
>>>> results from the return value on the do default in runtime than in
>>>> development.
>>>> Can someone tell me what I should expect from the return value on a 
>>>> default? Is it boolean, numeric, etc? It seems to be returning a 
>>>> (like '').
>>>> Thanks.
>>> _____________________________________________________________
>>> Manage your list subscriptions at http://lists.omnis-dev.com
>> _____________________________________________________________
>> Manage your list subscriptions at http://lists.omnis-dev.com
>Manage your list subscriptions at http://lists.omnis-dev.com

Phil Potter <phil at pgpotter.demon.co.uk>
Based in Chester in the UK

More information about the omnisdev-en mailing list