Re: Database Locking?!?

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 26127
interpreted = N
texte = >This has been discussed before and I'm bringing it up again... > >Database locking. >Let me make a few quick assumptions for my problem to prevent solutions >that I can't use: >1. I MUST use my sequential number solution as the record ID. >2. Refer to #1 >3. I can't really reduce the size of the database for other reasons. > >My question is, I need to do database locking somehow. If I do my >search INSIDE of the append, will that lock access to the database until >the append completes, and therefore solve my duplicate ID problem? > >If not, any other ideas on this (but sticking to the top 3 assumptions)?Use a second database that only has the highest number in it. So for each record in the other db get the number, put it in a variable then add one to it and append it back. Use a lookup to get the number the first time and a replace to append the incremented number. This would be a very fast way to take care of it.John Jakovich | ==Ecommerce and Beyond== Smith Micro Software Inc. | http://www.smithmicro.com------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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 Associated Messages, from the most recent to the oldest:

    
  1. Re: Database Locking?!? (Smith Micro Support 2000)
  2. Re: Database Locking?!? ( 2000)
  3. Database Locking?!? (Howard Wolosky 2000)
  4. Re: Database Locking?!? (Conley Hanson 2000)
>This has been discussed before and I'm bringing it up again... > >Database locking. >Let me make a few quick assumptions for my problem to prevent solutions >that I can't use: >1. I MUST use my sequential number solution as the record ID. >2. Refer to #1 >3. I can't really reduce the size of the database for other reasons. > >My question is, I need to do database locking somehow. If I do my >search INSIDE of the append, will that lock access to the database until >the append completes, and therefore solve my duplicate ID problem? > >If not, any other ideas on this (but sticking to the top 3 assumptions)?Use a second database that only has the highest number in it. So for each record in the other db get the number, put it in a variable then add one to it and append it back. Use a lookup to get the number the first time and a replace to append the incremented number. This would be a very fast way to take care of it.John Jakovich | ==Ecommerce and Beyond== Smith Micro Software Inc. | http://www.smithmicro.com------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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 Smith Micro Support

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:

Not really WebCat - need HTML Grider (1997) Showif, Hideif reverse logic ? (1997) WebCatalog Mac 2.1b3 (1997) WebCat2b13MacPlugIn - [showif][search][/showif] (1997) RE: MacFinder -- a new WebDNA web site (1998) Strange Question (2003) WebCat2 several catalogs? (1997) [OT] Server check please (2006) Secure server question (1997) SuperFlush stumped on simple sort (1999) ODBC / Paradox help needed (2005) Latest beta slow on [order] and [purchase] (1997) [date] +1 (1999) Looking for WebCat developer/contractor (2000) Dates (1996) Server slowing down. (1997) WebMerchant Q (2000) WebCat2b13MacPlugIn - more [date] problems (1997) WebDNA Solutions ... sorry! (1997) RE: Dates! (1998)