Re: Arbitrary limits on length of data in cart header fields?
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 26220
interpreted = N
texte = On 1/18/00 8:03 am, jpeacock@univpress.com so noted...>Just for your further edification, because of the way that WebCat displays IP >addresses, _all_ IP addresses are exactly 15 characters long >(999.999.999.999).Yes. That's what I meant by saying that if I was trying to store an IP address under CartIPAddress that was longer than 15 characters, I obviously must have some fairly serious bug in my code that the field limitation may mask (it certainly wouldn't *help* : )>As for your question about field lengths, PCS will need to document any >fields >that are not explicitly listed in the on-line docs (under the Purchase >command).Since the only limit mentioned in the docs is the 255 character limit for the Header fields, I had assumed all fields had the same limitation -- my mistake. I'd dearly like SM to outline the limits of the other fields.> I can tell you that it is always faster to use fixed length fields. I >suspect >if you have already used up 40 * 255 bytes in the Header fields that you >need to >revisit your database design. If you had a secondary database, tied by Cart >number to the Order File, you would still have RAM speed access to your >data. >What are you trying to store in the Header fields, if I may be so bold?I haven't used up all the available bytes in the Header fields, but I do have them set aside for 40 separate items of data. Short of doubling up the data on each (ok, one *does* hold 5 items that later get split apart with [listwords]) I thought I could make do with some of my unused named fields.I'm using the header fields within the site for a few saved state values, and during the final ordering process to store customer data over several pages of forms (without including a few dozen hidden form fields to bucket-brigade them along each page). I *could* modify the site to use a cart number-linked secondary database to hold this info, but why, when I have the primary database of the Order File right there already? I just need to know how much junk I can put into its various nooks and crannies ; )P.S. I had made a suggestion on the beta list a couple months back along the lines of doing for the Order File what WebCat 2.0 did for databases, giving user-control over the number and name of header fields. Sure would like to see *that* one come to be : ) Rob Marquardt Designer/Resident Wirehead Toast Design800 Washington Avenue North Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.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:
On 1/18/00 8:03 am, jpeacock@univpress.com so noted...>Just for your further edification, because of the way that WebCat displays IP >addresses, _all_ IP addresses are exactly 15 characters long >(999.999.999.999).Yes. That's what I meant by saying that if I was trying to store an IP address under CartIPAddress that was longer than 15 characters, I obviously must have some fairly serious bug in my code that the field limitation may mask (it certainly wouldn't *help* : )>As for your question about field lengths, PCS will need to document any >fields >that are not explicitly listed in the on-line docs (under the Purchase >command).Since the only limit mentioned in the docs is the 255 character limit for the Header fields, I had assumed all fields had the same limitation -- my mistake. I'd dearly like SM to outline the limits of the other fields.> I can tell you that it is always faster to use fixed length fields. I >suspect >if you have already used up 40 * 255 bytes in the Header fields that you >need to >revisit your database design. If you had a secondary database, tied by Cart >number to the order file, you would still have RAM speed access to your >data. >What are you trying to store in the Header fields, if I may be so bold?I haven't used up all the available bytes in the Header fields, but I do have them set aside for 40 separate items of data. Short of doubling up the data on each (ok, one *does* hold 5 items that later get split apart with [listwords]) I thought I could make do with some of my unused named fields.I'm using the header fields within the site for a few saved state values, and during the final ordering process to store customer data over several pages of forms (without including a few dozen hidden form fields to bucket-brigade them along each page). I *could* modify the site to use a cart number-linked secondary database to hold this info, but why, when I have the primary database of the order file right there already? I just need to know how much junk I can put into its various nooks and crannies ; )P.S. I had made a suggestion on the beta list a couple months back along the lines of doing for the order file what WebCat 2.0 did for databases, giving user-control over the number and name of header fields. Sure would like to see *that* one come to be : ) Rob Marquardt Designer/Resident Wirehead Toast Design800 Washington Avenue North Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.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
Rob Marquardt
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:
Is this possible, WebCat2.0 and checkboxes (1997)
Browser based content... (2004)
Robert Minor duplicate mail (1997)
[WebDNA] CSS HTML Email Using Emailer (2010)
WC2f3 (1997)
Deleting Multiple Database Records based on Checkbox (1998)
zip code vs tax rate database request (2002)
Here we go again... was: DDEConnect not working (2006)
Developer Edition - Connection Limit (2006)
TaxTotal Problem (1997)
Database causes out of memory error (2000)
apparently to problem isolated (1997)
Multiple catalog databases and showcart (1997)
Which GUI HTML editors work with WC ? (1997)
Error Lob.db records error message not name (1997)
WebCat2 - Getting to the browser's username/password data (1997)
taxTotal, too (1997)
Country & Ship-to address & other fields ? (1997)
using showpage and showcart commands (1996)
How did *you* learn Web Catalog? (2000)