Re: several people editing a database.

This WebDNA talk-list message is from

2001


It keeps the original formatting.
numero = 38923
interpreted = N
texte = What I use is a version control field as part of each record stored in the database. The version control field is a date-time stamp using the math function to convert date and time to numbers.When a user draws the record down to edit ... The version control number is tagged with the page. If he updates or change the record ... The attached version control number is transmitted with the changes where using showif or if statements in the acknowledgement page .... You can then direct the action to follow.The first thing upon submitting the change ... The acknowledgement page test to see if the record version control number is the same. If it is ... Then the change is effected to the record and a new version control control number appended. If it is not ... You can then inform the user that someone else has recently updated the record ... Present him with the extract of the updated record for editing or follow-up. As you can see, if some other user draws the record down after the first user ... Makes the change before the first user did his ... The version control number will change.Very simple but effective control mechanism. If a record has many fields, we further breakdown the edit page to present block entries (i.e. Sections where each section is a form covering a subset the fields for that record to change). This is better since we are also minimizing the amount of data exchange between client and server instead of the entire record. With sections, each can have their own version control number as well which means that 2 party updating different sections of the same record will not over ride one another without prior knowledge.Hope that helps ... TDn=========== From: dale Reply-To: (WebCatalog Talk) Date: Wed, 26 Sep 2001 16:33:11 To: (WebCatalog Talk) Subject: Re: several people editing a database.Whoever saves last wins. You would need to implement some sort of record locking, e.g. When someone is in edit mode, update a flag field in the database that does not let anyone else edit it. Kind of like a pre-edit. Then on saving of the field, clear the flag.The only problem is that if someone just views the details without editing it you could leave that flag set. Maybe add a second field with a time/date stamp and have a trigger run say each hour and clear the flag on any field more than xx minutes old.Daleon 9/26/01 4:27 PM, Donovan Brooke at dbrooke@ehg.net wrote:quick quesiton: any input as to whether or not letting mutiple people administer some of the databases is O.K.? if two people are editing the same record what happens? thx. -- Donovan D. Brooke Systems Administrator/ Assc. Art Director Epsen Hillmer Graphics ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: several people editing a database. (Terry Nair 2001)
  2. Re: several people editing a database. (dale 2001)
  3. several people editing a database. (Donovan Brooke 2001)
What I use is a version control field as part of each record stored in the database. The version control field is a date-time stamp using the math function to convert date and time to numbers.When a user draws the record down to edit ... The version control number is tagged with the page. If he updates or change the record ... The attached version control number is transmitted with the changes where using showif or if statements in the acknowledgement page .... You can then direct the action to follow.The first thing upon submitting the change ... The acknowledgement page test to see if the record version control number is the same. If it is ... Then the change is effected to the record and a new version control control number appended. If it is not ... You can then inform the user that someone else has recently updated the record ... Present him with the extract of the updated record for editing or follow-up. As you can see, if some other user draws the record down after the first user ... Makes the change before the first user did his ... The version control number will change.Very simple but effective control mechanism. If a record has many fields, we further breakdown the edit page to present block entries (i.e. Sections where each section is a form covering a subset the fields for that record to change). This is better since we are also minimizing the amount of data exchange between client and server instead of the entire record. With sections, each can have their own version control number as well which means that 2 party updating different sections of the same record will not over ride one another without prior knowledge.Hope that helps ... TDn=========== From: dale Reply-To: (WebCatalog Talk) Date: Wed, 26 Sep 2001 16:33:11 To: (WebCatalog Talk) Subject: Re: several people editing a database.Whoever saves last wins. You would need to implement some sort of record locking, e.g. When someone is in edit mode, update a flag field in the database that does not let anyone else edit it. Kind of like a pre-edit. Then on saving of the field, clear the flag.The only problem is that if someone just views the details without editing it you could leave that flag set. Maybe add a second field with a time/date stamp and have a trigger run say each hour and clear the flag on any field more than xx minutes old.Daleon 9/26/01 4:27 PM, Donovan Brooke at dbrooke@ehg.net wrote:quick quesiton: any input as to whether or not letting mutiple people administer some of the databases is O.K.? if two people are editing the same record what happens? thx. -- Donovan D. Brooke Systems Administrator/ Assc. Art Director Epsen Hillmer Graphics ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Terry Nair

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Pithy questions on webcommerce & siteedit (1997) List dead? (2000) Date problems-more (1997) Stupid question (2003) PCS Frames (1997) # of real domains on 1 web server (1997) You are not allowed to change the price (2003) [WebDNA] v6.2 or v7.x (2011) Multiple fields on 1 input (1997) I found a bug ... (1997) HomePage Caution (1997) using showpage and showcart commands (1996) Bug? (1997) Dates - Search and Sorting (1999) Help! WebCat2 bug (1997) PIXO support (1997) Simple Store (2000) Bad card db - *mislabled post* (1999) formula inside database to calculate weights (1997) WebSTAR 2.1 freezes my Mac (1997)