Shouldn't these updates/inserts be wrapped in a database transaction anyway?
Wouldn't that avoid the threading issues that are coming up?

On Tuesday, November 5, 2002, at 02:24 PM, Roger Haase wrote:

I fixed the problem by putting a rather brutal lock in ObjectStore, but
I would be happy to try your patch and grap a fresh copy of CVS at the
same time.

I was wondering if a more elegant solution would be to make MiddleKit
inserts and deletes commit to the database immediately and offer an
update option along the lines of what Ian discussed a while back which
would also cause an immediate commit.  I am too lazy to find the
original, it was a syntax like:
   row.update(a=1,b=2,c=3...)

I am not sure of the performance issues of this, plus or minus, but it
would be easier to explain.

Roger


-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to