Record Locking Postgres

Das Goravani goravanis at
Sun Jul 3 17:28:17 UTC 2022

> On Jul 3, 2022, at 12:51 PM, dlr at wrote:
> I use a standard set of routines to manage transactions in Omnis

Dear Dan,

When converting my astrology app to SQL, I made a set of routines that mimicked the Omnis data handling commands for the Datafiles. This worked out very well. I put the routines into the Table Superclass. I call an object that has the beginnings of the methods inside it.. here I would define the list from a SQL class.. this connected a Table Class which has the rest of the methods in it. I then would transfer from the Object to the Table class to finish the method. This may have been unnecessarily complex. I might have done just as well doing the whole method in the object. Since the Javascript Client only allows instance variables in fields on the form, or columns from an instance variable row, so your data is really locked in the form.. I’m not sure at this point if I could move the data from the form to say a Task Var Row so that the object containing centralized method would have access to the data being saved. I digress a bit here. Since your data with forms is locked in the form in instance variables, before calling a method in an object which attempts to save that data I envision one would have to copy the data to a Task Variable row that the object then has access to. Does this sound reasonable?

Where do you put your centralized methods? In an object, a Table, or where?

Can you use standard Objects when working the Javascript Client? (Said another way, do Remote Objects mean that standard objects cannot be used with the Javascript Client?) I’m assuming you CAN use normal Objects when working with Remote Forms. 

What do your calls to your centralized data handling methods look like?

Is it:

Do MyTaskVarObject.$MethodName(param1, param2…)



More information about the omnisdev-en mailing list