Re: [WebDNA] Re: table comma field delimiter bug?
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108103
interpreted = N
texte = Chris,Please keep the "," feature in databases.Deprecate the comma delimiter in tables.MattOn 1/13/2012 4:48 AM, christophe.billiottet@webdna.us wrote:> Hi everybody! interesting thread. I just did some tests myself and also= found that commas were interpreted as field delimiters in tables. I do n=ot think it is a bug, but it is an inconsistency.>> http://www.webdna.us/page.dna?numero=3D214>> Here an ex:>> "PCS","11770, Bernardo Plaza Court","San Diego","CA","92128">> At this time the comma in the street field is interpreted as delimiter.= It clearly should not.>> Since my plans are to =91normalize=92 inconsistencies in current WebDNA= language in the next versions, i have a listing of all notes and request=s found on this talk-list during the last 3 years.>> In this case, and in order to keep [table] and database format on par> - should we deprecate the comma field delimiters in tables?> - should we deprecate the comma field delimiters in databases and table=s?> - should we enforce the comma field delimiters in databases and tables =by using "," (a comma surrounded by two quotation marks)? in this case, t=he quotation mark would become an essential part of the database/table fo=rmat, and the lack of a single quotation mark would "break" the database =format.>>>> - chris>>>>> On Jan 13, 2012, at 5:34, Tom Duke wrote:>>> Ken,>>>> Hi - I have experienced the same issues as yourself. The discussion =at the time clarified that commas were interpreted as field delimiters wi=thin tables and could not be used.>>>> The simplest way to deal with this is to set up your table but then ad=d data using [append] and [url]'ing the values.>>>> - Tom>> --------------------------------------------------------- This message= is sent to you because you are subscribed to the mailing list . To unsub=scribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bu=g Reporting: support@webdna.us> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list
.> To unsubscribe, E-mail to:> archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us>>>> --=20> Matthew A Perosi> Corporate Consultant> Mobile Marketing Expert> Senior Web Developer> SEO Analyst& Educator>> Psi Prime, Inc.> 323 Union Blvd.> Totowa, NJ 07512>> Service: 973.413.8211> Training: 973.413.8214> Fax: 973.413.8217>> http://www.perosi.com
Associated Messages, from the most recent to the oldest:
Chris,Please keep the "," feature in databases.Deprecate the comma delimiter in tables.MattOn 1/13/2012 4:48 AM, christophe.billiottet@webdna.us wrote:> Hi everybody! interesting thread. I just did some tests myself and also= found that commas were interpreted as field delimiters in tables. I do n=ot think it is a bug, but it is an inconsistency.>> http://www.webdna.us/page.dna?numero=3D214>> Here an ex:>> "PCS","11770, Bernardo Plaza Court","San Diego","CA","92128">> At this time the comma in the street field is interpreted as delimiter.= It clearly should not.>> Since my plans are to =91normalize=92 inconsistencies in current WebDNA= language in the next versions, i have a listing of all notes and request=s found on this talk-list during the last 3 years.>> In this case, and in order to keep [table] and Database format on par> - should we deprecate the comma field delimiters in tables?> - should we deprecate the comma field delimiters in databases and table=s?> - should we enforce the comma field delimiters in databases and tables =by using "," (a comma surrounded by two quotation marks)? in this case, t=he quotation mark would become an essential part of the database/table fo=rmat, and the lack of a single quotation mark would "break" the database =format.>>>> - chris>>>>> On Jan 13, 2012, at 5:34, Tom Duke wrote:>>> Ken,>>>> Hi - I have experienced the same issues as yourself. The discussion =at the time clarified that commas were interpreted as field delimiters wi=thin tables and could not be used.>>>> The simplest way to deal with this is to set up your table but then ad=d data using [append] and [url]'ing the values.>>>> - Tom>> --------------------------------------------------------- This message= is sent to you because you are subscribed to the mailing list . To unsub=scribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bu=g Reporting: support@webdna.us> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list.> To unsubscribe, E-mail to:> archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us>>>> --=20> Matthew A Perosi> Corporate Consultant> Mobile Marketing Expert> Senior Web Developer> SEO Analyst& Educator>> Psi Prime, Inc.> 323 Union Blvd.> Totowa, NJ 07512>> Service: 973.413.8211> Training: 973.413.8214> Fax: 973.413.8217>> http://www.perosi.com
"Psi Prime Inc, Matthew A Perosi "
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:
Instructions for Digest (1997)
Templates for Customer Database? (1997)
Annoying character on writefile... (2004)
wish list (2002)
back button problem (1999)
[WebDNA] email validation (2019)
WebCatalog 2.0 & WebDNA docs in HTML ... (1997)
notification solutions (1997)
Exclamation point (1997)
[SearchString] problem with [search] context (1997)
Database Updates (1997)
Help name our technology! I found it (1997)
Links and Carriage Returns, Oh my! (2000)
cookies (2002)
DataBaseHelper Flawed (1997)
change the number format (1997)
SSL and Webstar 3 with Webcatalog (1998)
processing .html pages (2001)
WebCat editing, SiteGuard WAS:SiteAssociative lookup style? (1997)
Discounts (1998)