I don't know why webdna was ever coded to require two different formats= for field names and field values in csv files, but it seems like a foolish= way to do it -- because it is NOT consistent with tab-delimited format whi=ch uses tabs to separate both field names *and* field values.
What I got from my online bank was a file that had both the field values an=d the field names separated by commas. =A0It failed in webdna. =A0Then I mo=dified the file by surrounding all the commas with quotes to make it a &quo=t;quote-comma-quote" separated file. =A0This also failed in webdna.
According to your example we must use ONLY commas to separate field names, =then we have to use commas surrounded by quotes to separate field values. ==A0In other words, we have to use two different formats if we expect webdna= to work properly with csv files.
Why are we required to use two different formats in the same file in order =for webdna to use that file successfully as one of its databases???
Personally I think it would "make sense" to re-code webdna so tha=t it can handle csv files that use ONLY commas as separators for both field= names and field values, and so that it cal also handle csv files that use =commas surrounded by quotes as separators for both field names and field va=lues -- since these are the typical ways csv files are formatted in the ind=ustry (in my experience anyways).
By the way, I'm assuming that the different format requirement for fiel=d names vs. field values is the cause of my problem. =A0Is this the actual =cause ... or is something else going on here?
Sincerely,
Kenneth Grome
> Hello everybody, and particularely Ken, Matt and Stuart. We would not =like to leave a bug if there is a problem with the Merge format. Please, co=uld you confirm there is indeed a problem of databases not read using this =format? in this case, woud you be so kind to post the field names format an=d one or two lines of your databases.
>
> As explained in WebDNA website, the proper format is
>
> ----------------------------------------------------------------
> name,address,city,state,zip
> "Grant","1180 Central Ave","San Marcos",="CA","92079"
> "PCS","11770 Bernardo Plaza Court","San Diego=","CA","92128"
> ----------------------------------------------------------------
>
> and it works, at least for me. Here a small test: just upload this to =any WebDNA served website and open "states2.dna" file with your b=rowser.
>
>-----------------------------=----------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g=t;.
To unsubscribe, E-mail to: <talk=-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
old archives: http://dev.webdna.us/TalkListArchive/
Bug Reporting: http://forum.webdna.us/eucabb.html?pa=ge=3Dtopics&category=3D288
|
I don't know why webdna was ever coded to require two different formats= for field names and field values in csv files, but it seems like a foolish= way to do it -- because it is NOT consistent with tab-delimited format whi=ch uses tabs to separate both field names *and* field values.
What I got from my online bank was a file that had both the field values an=d the field names separated by commas. =A0It failed in webdna. =A0Then I mo=dified the file by surrounding all the commas with quotes to make it a &quo=t;quote-comma-quote" separated file. =A0This also failed in webdna.
According to your example we must use ONLY commas to separate field names, =then we have to use commas surrounded by quotes to separate field values. ==A0In other words, we have to use two different formats if we expect webdna= to work properly with csv files.
Why are we required to use two different formats in the same file in order =for webdna to use that file successfully as one of its databases???
Personally I think it would "make sense" to re-code webdna so tha=t it can handle csv files that use ONLY commas as separators for both field= names and field values, and so that it cal also handle csv files that use =commas surrounded by quotes as separators for both field names and field va=lues -- since these are the typical ways csv files are formatted in the ind=ustry (in my experience anyways).
By the way, I'm assuming that the different format requirement for fiel=d names vs. field values is the cause of my problem. =A0Is this the actual =cause ... or is something else going on here?
Sincerely,
Kenneth Grome
> Hello everybody, and particularely Ken, Matt and Stuart. We would not =like to leave a bug if there is a problem with the Merge format. Please, co=uld you confirm there is indeed a problem of databases not read using this =format? in this case, woud you be so kind to post the field names format an=d one or two lines of your databases.
>
> As explained in WebDNA website, the proper format is
>
> ----------------------------------------------------------------
> name,address,city,state,zip
> "Grant","1180 Central Ave","San Marcos",="CA","92079"
> "PCS","11770 Bernardo Plaza Court","San Diego=","CA","92128"
> ----------------------------------------------------------------
>
> and it works, at least for me. Here a small test: just upload this to =any WebDNA served website and open "states2.dna" file with your b=rowser.
>
>-----------------------------=----------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g=t;.
To unsubscribe, E-mail to: <talk=-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
old archives: http://dev.webdna.us/TalkListArchive/
Bug Reporting: http://forum.webdna.us/eucabb.html?pa=ge=3Dtopics&category=3D288
DOWNLOAD WEBDNA NOW!
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...