Re: Same DB Same Time
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 55969
interpreted = N
texte = Hey man thanks for replying. Yes, I actually switched my code back to =including the engine instead of using the almighty iFrame. An include was =my original plan. What stopped me from using it was some error checking =variables I had in the engine that I've since removed (allowing me to once =again go back to the include).Now I know that iFrames are not the best way to achieve what I want. =Thanks to everyone who helped me understand why the iFrame is a bad idea in= this situation.Thanks to everyone who helped me out.Justin CarrollOn Tuesday, March 30, 1943, Matthew C. Bohne
=wrote:>Does it have to be in an iframe? Couldn't you just do multiple>includes of the same file, changing variables as needed?>>[text show=3Df]section=3D1[/text]>[text show=3Df]banner_width=3D468[/text]>[text show=3Df]banner_height=3D60[/text]>[include banners.inc]>>[text show=3Df]section=3D2[/text]>[text show=3Df]banner_width=3D117[/text]>[text show=3Df]banner_height=3D240[/text]>[include banners.inc]>>>>>---- Original Message ---->From: justincarroll@sanduskyregister.com>To: WebDNA-Talk@talk.smithmicro.com>Subject: RE: Same DB Same Time>Date: 09 Feb 2004 11:57:14 -0500>>>I have two iFrames on a page. Both of the iFrame's src is the same.=20>>It is a .tpl page that does a [replacefounditems] on one database and>>an [append] on another database.>>>>The [replacefounditems] pulls an integer from the database, increases>>it by one, and then replaces the old value. The [append] creates a>>new sku by grabbing the highest integer and increasing it by one>>(basically an autonumber).>>>>Sometimes this all works just fine with the same .tpl firing at the>>same time, accessing the same db at the same time and updating at the>>same time; however, sometimes it does not. In the case that it does>>not, I get duplicate skus and the integer that is supposed to be>>updated by the [replacefounditems] does not update.>>>>I've tested this numerous times (a lot). It acts like the two>>statements fire and collide with each other. Or that one isn't>>commiting in time for the other statement to realize anything has>>changed in the database. It seems like WebDNA should have some sort>>of buffer for accessing the same database at the same time.>>>>I've wrote the talk list about this problem before and haven't come>>up with any great solution. I'd like to give this another whirl and>>see if we can't find something. Please help. Thanks.>>>>Justin Carroll>>>>>>>>------------------------------------------------------------->>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://webdna.smithmicro.com/>>---->"I've never known a musician who regretted being one. Whatever=20>else life gives you, music will never let you down.>>>------------------------------------------------------------->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://webdna.smithmicro.com/>-------------------------------------------------------------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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Hey man thanks for replying. Yes, I actually switched my code back to =including the engine instead of using the almighty iFrame. An include was =my original plan. What stopped me from using it was some error checking =variables I had in the engine that I've since removed (allowing me to once =again go back to the include).Now I know that iFrames are not the best way to achieve what I want. =Thanks to everyone who helped me understand why the iFrame is a bad idea in= this situation.Thanks to everyone who helped me out.Justin CarrollOn Tuesday, March 30, 1943, Matthew C. Bohne =wrote:>Does it have to be in an iframe? Couldn't you just do multiple>includes of the same file, changing variables as needed?>>[text show=3Df]section=3D1[/text]>[text show=3Df]banner_width=3D468[/text]>[text show=3Df]banner_height=3D60[/text]>[include banners.inc]>>[text show=3Df]section=3D2[/text]>[text show=3Df]banner_width=3D117[/text]>[text show=3Df]banner_height=3D240[/text]>[include banners.inc]>>>>>---- Original Message ---->From: justincarroll@sanduskyregister.com>To: WebDNA-Talk@talk.smithmicro.com>Subject: RE: Same DB Same Time>Date: 09 Feb 2004 11:57:14 -0500>>>I have two iFrames on a page. Both of the iFrame's src is the same.=20>>It is a .tpl page that does a [replacefounditems] on one database and>>an [append] on another database.>>>>The [replacefounditems] pulls an integer from the database, increases>>it by one, and then replaces the old value. The [append] creates a>>new sku by grabbing the highest integer and increasing it by one>>(basically an autonumber).>>>>Sometimes this all works just fine with the same .tpl firing at the>>same time, accessing the same db at the same time and updating at the>>same time; however, sometimes it does not. In the case that it does>>not, I get duplicate skus and the integer that is supposed to be>>updated by the [replacefounditems] does not update.>>>>I've tested this numerous times (a lot). It acts like the two>>statements fire and collide with each other. Or that one isn't>>commiting in time for the other statement to realize anything has>>changed in the database. It seems like WebDNA should have some sort>>of buffer for accessing the same database at the same time.>>>>I've wrote the Talk List about this problem before and haven't come>>up with any great solution. I'd like to give this another whirl and>>see if we can't find something. Please help. Thanks.>>>>Justin Carroll>>>>>>>>------------------------------------------------------------->>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://webdna.smithmicro.com/>>---->"I've never known a musician who regretted being one. Whatever=20>else life gives you, music will never let you down.>>>------------------------------------------------------------->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://webdna.smithmicro.com/>-------------------------------------------------------------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://webdna.smithmicro.com/
Justin Carroll
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:
OT: Processor Speed (2002)
Re:quit command on NT (1997)
Webcat & SIMS (1998)
2nd WebCatalog2 Feature Request (1996)
portal (2002)
emailer prob (1998)
OT: Limit on # of Pulldown entries (1997)
Showif for mulitple variations (1997)
Special characters & [sendmail] (1998)
Multiple security dbs (1997)
Fun with Dates - revisited (1997)
same product in cart (1997)
Price Hacking (1998)
Emailer port change (1997)
Anyone have an invoicing system? (2000)
Search Results (1998)
frames & carts (1997)
Width & Height (1998)
Line items in table cells (1997)
Problems searching from a FORM (1997)