CapableObjects forum » ECO » General discussions » Too frequent calls to UpdateDatabase() in ECO ASP.NET app

Too frequent calls to UpdateDatabase() in ECO ASP.NET app

OZh — Sat, 26 Jun 2010 16:40:51 GMT

Hi all,

I'm writing a small ASP.NET application. As I understand the EcoSpaceManager throws an exception during page unload if there are dirty objects.

One option to avoid this exception is to call EcoSpace.UpdateDatabase() after each change to ECO objects. But it will result in too many calls to UpdateDatabase().

What's the preferred practice to minimize the number of calls to UpdateDatabase() ?

Thanks,
--
Oleg Zhukov

RE: Too frequent calls to UpdateDatabase() in ECO ASP.NET app

Peter Morris — Sat, 26 Jun 2010 16:40:51 GMT

[quote][b]OZh (2010-06-26)[/b][hr]Why not updating DB automatically before unloading the page?

I mean why I should remember to call UpdateDatabase() myself if it can be hooked to some page lifecycle event?[/quote]

So when the user clicks "Cancel" you want the page unload event to update the DB? :)

Save at the point the user has completed a single logical operation.

RE: Too frequent calls to UpdateDatabase() in ECO ASP.NET app

mtiede — Sat, 26 Jun 2010 15:51:43 GMT

Maybe the user has changed their mind and he DOESN'T want to save the changes just because he is leaving the page?

RE: Too frequent calls to UpdateDatabase() in ECO ASP.NET app

OZh — Sat, 26 Jun 2010 13:26:40 GMT

Why not updating DB automatically before unloading the page?

I mean why I should remember to call UpdateDatabase() myself if it can be hooked to some page lifecycle event?

RE: Too frequent calls to UpdateDatabase() in ECO ASP.NET app

Peter Morris — Thu, 24 Jun 2010 10:20:45 GMT

[quote][b]OZh (2010-06-24)[/b][hr]Hi all,

I'm writing a small ASP.NET application. As I understand the EcoSpaceManager throws an exception during page unload if there are dirty objects.

One option to avoid this exception is to call EcoSpace.UpdateDatabase() after each change to ECO objects. But it will result in too many calls to UpdateDatabase().

What's the preferred practice to minimize the number of calls to UpdateDatabase() ?

Thanks,
--
Oleg Zhukov[/quote]

Only update the DB after you change something. Also, updating the DB when there are no dirty objects will do nothing.