Re: Same DB Same Time
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 55958
interpreted = N
texte = On 2/9/04 1:17 PM, "John Peacock"
wrote:> You can ask your doctor to adjust your medication so the people in your head> don't talk so loud then. ;~)Shock therapy:-)> I suspect in the case Justin was describing (banner rotation), there is no> reason to have any visible evidence that [cart] is being used internally. Not> many people complain that the ASP session id value is a useless string of> characters and numbers, since that is not usually exposed in any way.Actually its not the 'viewing of it'.We are pretty anal about memory usage. I have found you need to be,especially on ram based stuff.Using the cart number for record numbers is often like rabbit hunting withan elephant gun.Once you start getting into record counts of 50,000, or 100,000 or 250,000you realize that a sku number of "3285322251348916" * 100,000+ records ispretty poor memory management.Now we rarely start with 1, but we do commonly start with 1000. Don't ask mewhy... Old habit I guess.But over large databases you do start to see savings in both memory andperformance. I have always found it a bit humorous to watch some people go to GREATlengths to normalize as much as possible, yet use inflated identifiers, suchas cart.Don't get me wrong, CART has many many valuable uses, not the least of whichis a browser independent tracking system... But I personally don't use itfor record identifiers except in the low requirement situations.> In my experience, either a SKU has to mirror an external (to WebCat) system or> it just needs to be a monotonically increasing unique value (which is> suprisingly what the [cart] generates).Ah yes but "monotonically increasing unique value" is only true of the fewnumbers you implement at the page level... Then there are large andunpredictable gaps based on all the other 'carts' that are generatedelsewhere.Wow, never thought I would be discussing CART so much...Regardless, based on the original question and the 'dependency' on a inincremented scheme, he will run into trouble with the multiple frames...Lose the numbering scheme requirement and he will probably be fine.Time to up the dosage.;-)AlexAlex J McCombie New World MediaChief Information Officer Box 124888/892.6379 MartVille, NY 13111Alex@NewWorldMedia.com http://OurClients.comInterface Designer WebDNA Programmer Database Designer-------------------------------------------------------------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:
On 2/9/04 1:17 PM, "John Peacock" wrote:> You can ask your doctor to adjust your medication so the people in your head> don't talk so loud then. ;~)Shock therapy:-)> I suspect in the case Justin was describing (banner rotation), there is no> reason to have any visible evidence that [cart] is being used internally. Not> many people complain that the ASP session id value is a useless string of> characters and numbers, since that is not usually exposed in any way.Actually its not the 'viewing of it'.We are pretty anal about memory usage. I have found you need to be,especially on ram based stuff.Using the cart number for record numbers is often like rabbit hunting withan elephant gun.Once you start getting into record counts of 50,000, or 100,000 or 250,000you realize that a sku number of "3285322251348916" * 100,000+ records ispretty poor memory management.Now we rarely start with 1, but we do commonly start with 1000. Don't ask mewhy... Old habit I guess.But over large databases you do start to see savings in both memory andperformance. I have always found it a bit humorous to watch some people go to GREATlengths to normalize as much as possible, yet use inflated identifiers, suchas cart.Don't get me wrong, CART has many many valuable uses, not the least of whichis a browser independent tracking system... But I personally don't use itfor record identifiers except in the low requirement situations.> In my experience, either a SKU has to mirror an external (to WebCat) system or> it just needs to be a monotonically increasing unique value (which is> suprisingly what the [cart] generates).Ah yes but "monotonically increasing unique value" is only true of the fewnumbers you implement at the page level... Then there are large andunpredictable gaps based on all the other 'carts' that are generatedelsewhere.Wow, never thought I would be discussing CART so much...Regardless, based on the original question and the 'dependency' on a inincremented scheme, he will run into trouble with the multiple frames...Lose the numbering scheme requirement and he will probably be fine.Time to up the dosage.;-)AlexAlex J McCombie New World MediaChief Information Officer Box 124888/892.6379 MartVille, NY 13111Alex@NewWorldMedia.com http://OurClients.comInterface Designer WebDNA Programmer Database Designer-------------------------------------------------------------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/
Alex McCombie
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:
Attn: Bug in GeneralStore example b15 (1997)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
f2 download problems (1997)
Accented chars and emailer (1998)
Making a secret cookie code in WebCat (2001)
results in a table (2000)
Price recalc based on quantity (1997)
redirect with frames (1997)
Database Options (1997)
Form Weirdness (2002)
Execute Applescript (1997)
Showif probably dumb question (1997)
Web Catalog 2 demo (1997)
Simple way to create unique SKU (1997)
TeaRoom Search page (2000)
Search design (1997)
Newbie Tax Question (1997)
Access Denied! But why? (1997)
insecure client not shown (1998)
bug in [SendMail] (1997)