Re: [WebDNA] Query re: autonumber
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105531
interpreted = N
texte = > Ken, > > Thanks for that. I think I'll stick to using cart for record IDs > then. > > A follow up question, if I am doing a bulk append to a db then I can > only create one [cart] on a template, so if I use the following > within a search context am I safe in not creating duplicate cart IDs: > > [search db=import.db&neIDdatarq=find_all][founditems] > > [append db=appendto.db]recordID=[cart][index][/append] > > [/founditems][/search] > > Thanks > - Tom Hi Tom, in the situation you just asked about, I have been in the habit of writing the IDs like this: [founditems] [append db=appendto.db]recordID=[cart]_[index][/append] [/founditems] ...because unless one knows *exactly* how cart strings are created... and what all are their possible values.. then conceivably a cart string could have already in the past been what you were about to write with your current (this page render) [cart] concatenated with one more digit (the [index]). RIght? But by separating the [cart] from the [index] with the underscore, then you KNOW that the complete ID will be unique because the unadulterated [cart] is always unique, and after the underscore will be unique on each iteration of [founditems] (in the context of *that* [cart]). If someone argues my case here, and says you were safe the way you were about to do it.. then I presume that it means they know more than I do about the possible range of cart strings. There must have been discussion on list in the past about that... but I think I was away at that time. ------------ Govinda govinda.webdnatalk@gmail.com
Associated Messages, from the most recent to the oldest:
> Ken, > > Thanks for that. I think I'll stick to using cart for record IDs > then. > > A follow up question, if I am doing a bulk append to a db then I can > only create one
[cart] on a template, so if I use the following > within a search context am I safe in not creating duplicate cart IDs: > > [search db=import.db&neIDdatarq=find_all]
[founditems] > > [append db=appendto.db]recordID=
[cart][index][/append] > > [/founditems][/search] > > Thanks > - Tom Hi Tom, in the situation you just asked about, I have been in the habit of writing the IDs like this:
[founditems] [append db=appendto.db]recordID=
[cart]_[index][/append] [/founditems] ...because unless one knows *exactly* how cart strings are created... and what all are their possible values.. then conceivably a cart string could have already in the past been what you were about to write with your current (this page render)
[cart] concatenated with one more digit (the [index]). RIght? But by separating the
[cart] from the [index] with the underscore, then you KNOW that the complete ID will be unique because the unadulterated
[cart] is always unique, and after the underscore will be unique on each iteration of
[founditems] (in the context of *that*
[cart]). If someone argues my case here, and says you were safe the way you were about to do it.. then I presume that it means they know more than I do about the possible range of cart strings. There must have been discussion on list in the past about that... but I think I was away at that time. ------------ Govinda govinda.webdnatalk@gmail.com
Govinda
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:
Cart# (1997)
[WebDNA] Advices for Linux Config (2017)
Bug Report, maybe (1997)
Webcat Manual and TeaRoom Examples Uses Different Examples. (1997)
Problems searching from a FORM (1997)
Duplicate Carts (2000)
Virtual hosting and webcatNT (1997)
Re:Emailer problem....still (1997)
can WC render sites out? (1997)
A Couple Photos from the SmithMicro Booth at MacWorld (2000)
Kanji in http requests (1998)
Professional WebDNA Hosting Solutions (2005)
What's wrong with this? (2005)
Waitfor(ever) (2002)
Out of the woodwork (2007)
Email Format (1998)
Major Security Hole (1998)
Bug Report, maybe (1997)
Unexpected error (1997)
Am I going senile? (Price recalc based on quantity) (1997)