Re: [WebDNA] table comma field delimiter bug?
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108094
interpreted = N
texte = If I enter the data into the table as shown here, the commas are interpreted by WebDNA as field separators when I search the table. Naturally I can URL the field values by wrapping the [interpret][[fieldname]][/interpret] part in a URL context, and this actually defeats WebDNA's "table comma bug" because it never sees the commas, it only see the URLed comma values ... but then the data is displayed as URLed values on the web page, thus the reason why I have to UNURL them to get them to display properly. So like I said earlier, it's a bug ... or it's a mistake in the docs, whichever you want to call it ... but WebDNA is clearly seeing the commas as field delimiters even though the data is entered correctly as tab-delimited text. In my opinion it should not interpret commas as field separators in this situation, because the proper way to input data like this is ONLY to enter the data as tab-delimited text. Yes I know, I can probably input the data via a series of appends and not experience this problem. But the point is that the docs say I am entering the data correctly. So if WebDNA's internal code will not be changed in an effort to get rid of this "bug", then the docs should be changed so that they only allow data to be entered into a table via via append ... Or at least mention the fact that if you use the data input method shown in the docs, you cannot enter any commas unless you also URL the comma-filled fields going in, and then unurl them coming out. Sincerely, Kenneth Grome [table name=theData&fields=[getchars start=2&from=end][listfields db=source.db][fieldname],[/listfields] [/getchars]] [search db=source.db&neskudatarq=[blank]&rank=off][founditems][getchars start=2&from=end][listfields db=source.db][interpret][[fieldname]][/interpret] [/listfields][/getchars] [/founditems][/search][/table] [search table=theData&neskudatarq=[blank]&rank=off] [founditems] [/founditems] [/search] > still haven't seen any code.
Associated Messages, from the most recent to the oldest:
If I enter the data into the table as shown here, the commas are interpreted by WebDNA as field separators when I search the table. Naturally I can URL the field values by wrapping the
[interpret][[fieldname]][/interpret] part in a URL context, and this actually defeats WebDNA's "table comma bug" because it never sees the commas, it only see the URLed comma values ... but then the data is displayed as URLed values on the web page, thus the reason why I have to UNURL them to get them to display properly. So like I said earlier, it's a bug ... or it's a mistake in the docs, whichever you want to call it ... but WebDNA is clearly seeing the commas as field delimiters even though the data is entered correctly as tab-delimited text. In my opinion it should not interpret commas as field separators in this situation, because the proper way to input data like this is ONLY to enter the data as tab-delimited text. Yes I know, I can probably input the data via a series of appends and not experience this problem. But the point is that the docs say I am entering the data correctly. So if WebDNA's internal code will not be changed in an effort to get rid of this "bug", then the docs should be changed so that they only allow data to be entered into a table via via append ... Or at least mention the fact that if you use the data input method shown in the docs, you cannot enter any commas unless you also URL the comma-filled fields going in, and then unurl them coming out. Sincerely, Kenneth Grome [table name=theData&fields=[getchars start=2&from=end][listfields db=source.db][fieldname],[/listfields] [/getchars]] [search db=source.db&neskudatarq=[blank]&rank=off]
[founditems][getchars start=2&from=end][listfields db=source.db]
[interpret][[fieldname]][/interpret] [/listfields][/getchars] [/founditems][/search][/table] [search table=theData&neskudatarq=[blank]&rank=off]
[founditems] [/founditems] [/search] > still haven't seen any code.
Kenneth Grome
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 there an alternative to emailer? (1999)
[WebDNA] special chars (2009)
form data submission gets truncated (1997)
WebCatalog [FoundItems] Problem - AGAIN - (1997)
list items (1998)
How to redirect based on price subtotal? (1998)
form data submission gets truncated (1997)
writing db to disk (1997)
Random ads (1998)
[format xs] freeze (1997)
Error with [applescript] (1999)
self maintaining databases? (1998)
Notice (2003)
How to Sort Summ data ? (1997)
WebMerchant Error (1998)
HomePage Caution (1997)
WebCat2 several catalogs? (1997)
webten vs. webstar (1998)
Bit off subject -- Faxing orders (1997)
Happy New year (2004)