Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Optimistic Locking approach for Asp.Net

22 views
Skip to first unread message

Ingres Forums

unread,
Mar 12, 2015, 10:50:55 AM3/12/15
to

We're considering rewriting some of our 4GL applications to be ASP.Net
web pages. All of our 4GL applications use pessimistic locking.
We're looking for good approaches to rewriting them without having to
check say for example every field that was selected vs values when at
update time.

Is there anything like a rowver/timestamp in every Ingres table that we
could check against, etc?


--
kyledarrenhanson
------------------------------------------------------------------------
kyledarrenhanson's Profile: http://community.actian.com/forum/member.php?userid=394
View this thread: http://community.actian.com/forum/showthread.php?t=16919

Ingres Forums

unread,
Mar 12, 2015, 1:00:14 PM3/12/15
to

(Caveat: I know nothing about your application so I don't know why
preemptive exclusive locking is so important to you nor what the limits
on an acceptable solution are.)

You could probably rig up some kind of versioning using rules and
procedures pretty easily, though I wouldn't use version numbers or
timestamps. If I set up row versioning I'd probably tag the rows with
the transaction ID (*dbmsinfo('db_tran_id')*) that did the update. That
way I wouldn't get spurious rejections of updates to rows I'd just
updated myself.


--
rhann
------------------------------------------------------------------------
rhann's Profile: http://community.actian.com/forum/member.php?userid=131

nikosv

unread,
Mar 12, 2015, 4:33:14 PM3/12/15
to
check this node for a simillar case :

https://groups.google.com/forum/#!searchin/comp.databases.ingres/$20Optimistic$20concurrency$20in$20a$20pesimmistic$20environment$20|sort:relevance/comp.databases.ingres/nsvpJcpMonA/51F_8szme6EJ

Ingres Forums

unread,
Mar 12, 2015, 8:54:22 PM3/12/15
to

kyledarrenhanson;51241 Wrote:
> We're considering rewriting some of our 4GL applications to be ASP.Net
> web pages. All of our 4GL applications use pessimistic locking.
> We're looking for good approaches to rewriting them without having to
> check say for example every field that was selected vs values when at
> update time.
>
> Is there anything like a rowver/timestamp in every Ingres table that we
> could check against, etc?

Have you considered using the OpenROAD AppServer to expose the 4gl to
asp.net? That way the business logic stays the same and you only worry
about UI "stuff" in the web app.


--
clach04
------------------------------------------------------------------------
clach04's Profile: http://community.actian.com/forum/member.php?userid=648

Ingres Forums

unread,
Mar 17, 2015, 12:51:27 PM3/17/15
to

we haven't made use or have any experience with OpenRoad, but may be
worth a look, thanks.


--
kyledarrenhanson
------------------------------------------------------------------------
kyledarrenhanson's Profile: http://community.actian.com/forum/member.php?userid=394
0 new messages