To clarify my use of the locking. We have an ordering system that all the sales people have access to. I am trying to prevent Sales Person #1 from opening an order looking at it...Sales Person #2 opening the same order and making a change...Sales Person #1 saves his/her changes and overwrites Sales Person #2's changes. In addition this system uses legacy data which is in FoxPro free tables (this is not my choice). Hope this clarifies my question. ------------------------------------------------------------------------------- Ron Baum Database Engineer Accelerated Technology, Inc. 720 Oak Circle Dr East Mobile, AL 36609 Email: rbaum@atinucleus.com http://www.acceleratedtechnology.com ------------------------------------------------------------------------------- "Nucleus. All You NEED in an RTOS. Royalty Free." -------------------------------------------------------------------------------
As suggested this is normally handled at the change time. Put a date stamp in the record, when person 2 tries to commit the changes the data the record was last changed will be greater than when it is opened, hence they cant commit. -- Andy McKay. ----- Original Message ----- From: "Ron Baum" <rbaum@atinucleus.com> To: "Zope List" <zope@zope.org> Cc: "Yvonne Totty" <ytotty@atinucleus.com>; "Steven Grimes" <sgrimes@atinucleus.com> Sent: Wednesday, April 04, 2001 10:48 AM Subject: [Zope] Clarify Locking
To clarify my use of the locking.
We have an ordering system that all the sales people have access to. I am trying to prevent Sales Person #1 from opening an order looking at it...Sales Person #2 opening the same order and making a change...Sales Person #1 saves his/her changes and overwrites Sales Person #2's changes.
In addition this system uses legacy data which is in FoxPro free tables (this is not my choice).
Hope this clarifies my question. --------------------------------------------------------------------------
Ron Baum Database Engineer Accelerated Technology, Inc. 720 Oak Circle Dr East Mobile, AL 36609
Email: rbaum@atinucleus.com http://www.acceleratedtechnology.com --------------------------------------------------------------------------
"Nucleus. All You NEED in an RTOS. Royalty Free." --------------------------------------------------------------------------
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
I had actually come up a with a similar solution but I was hoping for a way to let users know that someone else was editing a record so that they would not have to waste time editing it and then have to refresh and try to edit it again. Ron ----- Original Message ----- From: Andy McKay To: Ron Baum ; Zope List Cc: Yvonne Totty ; Steven Grimes Sent: Wednesday, April 04, 2001 1:17 PM Subject: Re: [Zope] Clarify Locking As suggested this is normally handled at the change time. Put a date stamp in the record, when person 2 tries to commit the changes the data the record was last changed will be greater than when it is opened, hence they cant commit. -- Andy McKay. ----- Original Message ----- From: "Ron Baum" <rbaum@atinucleus.com> To: "Zope List" <zope@zope.org> Cc: "Yvonne Totty" <ytotty@atinucleus.com>; "Steven Grimes" <sgrimes@atinucleus.com> Sent: Wednesday, April 04, 2001 10:48 AM Subject: [Zope] Clarify Locking
To clarify my use of the locking.
We have an ordering system that all the sales people have access to. I am trying to prevent Sales Person #1 from opening an order looking at it...Sales Person #2 opening the same order and making a change...Sales Person #1 saves his/her changes and overwrites Sales Person #2's changes.
In addition this system uses legacy data which is in FoxPro free tables (this is not my choice).
Hope this clarifies my question. --------------------------------------------------------------------------
Ron Baum Database Engineer Accelerated Technology, Inc. 720 Oak Circle Dr East Mobile, AL 36609
Email: rbaum@atinucleus.com http://www.acceleratedtechnology.com --------------------------------------------------------------------------
"Nucleus. All You NEED in an RTOS. Royalty Free." --------------------------------------------------------------------------
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Well you could do that, if a user hasnt made a change in 5 mins say turn off the lock. Sounds hokey though. Can the if in doubt solve all solution, a java applet fix this? -- Andy McKay. ----- Original Message ----- From: "Ron Baum" <rbaum@atinucleus.com> To: "Andy McKay" <andym@ActiveState.com>; "Zope List" <zope@zope.org> Cc: "Yvonne Totty" <ytotty@atinucleus.com>; "Steven Grimes" <sgrimes@atinucleus.com> Sent: Wednesday, April 04, 2001 11:41 AM Subject: Re: [Zope] Clarify Locking
I had actually come up a with a similar solution but I was hoping for a way to let users know that someone else was editing a record so that they would not have to waste time editing it and then have to refresh and try to edit it again.
Ron ----- Original Message ----- From: Andy McKay To: Ron Baum ; Zope List Cc: Yvonne Totty ; Steven Grimes Sent: Wednesday, April 04, 2001 1:17 PM Subject: Re: [Zope] Clarify Locking
As suggested this is normally handled at the change time. Put a date stamp in the record, when person 2 tries to commit the changes the data the record was last changed will be greater than when it is opened, hence they cant commit. -- Andy McKay.
----- Original Message ----- From: "Ron Baum" <rbaum@atinucleus.com> To: "Zope List" <zope@zope.org> Cc: "Yvonne Totty" <ytotty@atinucleus.com>; "Steven Grimes" <sgrimes@atinucleus.com> Sent: Wednesday, April 04, 2001 10:48 AM Subject: [Zope] Clarify Locking
To clarify my use of the locking.
We have an ordering system that all the sales people have access to. I am trying to prevent Sales Person #1 from opening an order looking at it...Sales Person #2 opening the same order and making a change...Sales Person #1 saves his/her changes and overwrites Sales Person #2's changes.
In addition this system uses legacy data which is in FoxPro free tables (this is not my choice).
Hope this clarifies my question.
-------------------------------------------------------------------------- -----
Ron Baum Database Engineer Accelerated Technology, Inc. 720 Oak Circle Dr East Mobile, AL 36609
Email: rbaum@atinucleus.com http://www.acceleratedtechnology.com
-------------------------------------------------------------------------- -----
"Nucleus. All You NEED in an RTOS. Royalty Free."
-------------------------------------------------------------------------- -----
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Ron Baum wrote:
To clarify my use of the locking.
We have an ordering system that all the sales people have access to. I am trying to prevent Sales Person #1 from opening an order looking at it...Sales Person #2 opening the same order and making a change...Sales Person #1 saves his/her changes and overwrites Sales Person #2's changes.
In addition this system uses legacy data which is in FoxPro free tables (this is not my choice).
Hope this clarifies my question.
Yew, this clarifies your question. If you can't handle the lock at database level as in FoxPro tables, the solution that i figure out could be a shared object between all the users. Something like a thread semaphore in thread programming. I'll do some investigation on that hope this helps azazel
participants (3)
-
Alberto Berti -
Andy McKay -
Ron Baum