Re: Here we go again...
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66690
interpreted = N
texte = Yes that is what I am saying. Tab-delimited text files... It really =makes many non-webdna developers "wonder".-----Original Message-----From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf OfDan StrongSent: Saturday, April 01, 2006 10:02 AMTo: WebDNA TalkSubject: Re: Here we go again...I've also never used any flavor of SQL, but I've dabbled with Access -- =to the point where I=20realized I could do everything I was trying to do in WebDNA in about 1/4 =the time :)... yeah, I've=20tried to explain to non-webdna developers that I simply use tab-delimted =text files to do my thing=20and they just stare at me blankly... it's sort of funny to me now.-DanOn Sat, 1 Apr 2006 08:42:44 -0600 Pat McCormick
wrote:> Actually WebDNA doesn't use a flat file. That is the case for the =older Typhoon version, but=20>WebDNA, simply because it can have multiple databases open, is no =longer a flat file system.>=20> The difference is that WebDNA doesn't formalize the structure of a db =in any way. You are=20>responsible for define a sku or key field and there are some nice =tools to assist the process,=20>like [cart]. Comparing that with SQL or Access, those products get =more antsy about key fields,=20>and field formats in general. They also enforce the idea of a database =consisting of a=20>collection of tables, which is also confusing nonsense.>=20> The purpose for products like Oracle, SQL and other "databases" is to =encrypt your text so that=20>you need to buy their products to see your text. Web-DNA is the =un-database database. Create=20>your own relationships. All key fields are optional. Structure your =project any way you want,=20>even using virtual databases ([table]), and to make it even better, =keep all the data in plain=20>text so you can x-ray the files at any time using any text tool. Ya =gotta love that!>=20>=20>=20>=20>=20>=20> On Mar 31, 2006, at 2:12 PM, Bess Ho wrote:>=20>> WebDNA is using flat file for storing data. It is not a =20>> relationship database like MySQL. Also once your flat file grow =20>> beyond roughly 2 GB (check with Network Admin to verify the size), =20>> you can't run data very well. The go-around solution is to break =20>> down WebDNA database into smaller chunks for faster performance. =20>> You really need Relationship Database for scaleable application.>>>> -----Original Message----->> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf =Of>> Kenneth Grome>> Sent: Friday, March 31, 2006 4:55 AM>> To: WebDNA Talk>> Subject: Re: Here we go again...>>>>>> On Fri, 31 Mar 2006 07:05:55 -0500, Terry Wilson wrote:>>> ... you never know when you'll be required to start doing something =a>>> certain way; or at some point, an old solution just isn't good =enough>>> or fast enough any longer ...>>>>>> Example:>>>> A client of mine preferred webdna but his searches were too slow, =20>> so he hired me to debug and fix them. His code was fine but the =20>> database files were not configured to optimize webdna's =20>> performance, so I could only recommend two options: (1) =20>> reconfigure the databases (not a good solution because updated data =20>> files came from another source frequently) ... or (2) switch to =20>> MySQL and give that a try ...>>>> I really didn't know if MySQL could handle the task any faster than =20>> webdna and I told him this, but he went for it anyways. He said =20>> webdna hosting cost too much anyways, and since he wasn't committed =20>> to using it on his server anyways (although he enjoyed personally =20>> mocking up web sites because it's east for a non-programmer to use) =20>> he decided to go with PHP and MySQL.>>>> The moment we switched his search times dropped from about 10 =20>> seconds to less than two seconds. I think the reason is two-fold: =20>> (1) he had database files that were too large for webdna to RAM-=20>> cache efficiently, and (2) we were doing nested searches, and =20>> webdna is pretty slow sometimes when using nested searches, =20>> especially with large db files.>>>> The bottom line is that he "outgrew" webdna for use on his server, =20>> and now he's happy again with a faster free solution. I think this =20>> type of situation is going to become more and more common as webdna =20>> continues to be less and less aggressively developed, supported and =20>> marketed.>>>> Sincerely,>> Kenneth Grome>>>> owner@kengrome.com>> kengrome@gmail.com>> www.kengrome.com>>>>>>>>>>>>>> ------------------------------------------------------------->> 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 > digest@talk.smithmicro.com>>> Web Archive of this list is at: http://webdna.smithmicro.com/>>>> ------------------------------------------------------------->> 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 > digest@talk.smithmicro.com>>> Web Archive of this list is at: http://webdna.smithmicro.com/>>>=20>=20> -------------------------------------------------------------> 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/-------------------------------------------------------------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/-------------------------------------------------------------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:
Yes that is what I am saying. Tab-delimited text files... It really =makes many non-webdna developers "wonder".-----Original Message-----From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf OfDan StrongSent: Saturday, April 01, 2006 10:02 AMTo: WebDNA TalkSubject: Re: Here we go again...I've also never used any flavor of SQL, but I've dabbled with Access -- =to the point where I=20realized I could do everything I was trying to do in WebDNA in about 1/4 =the time :)... yeah, I've=20tried to explain to non-webdna developers that I simply use tab-delimted =text files to do my thing=20and they just stare at me blankly... it's sort of funny to me now.-DanOn Sat, 1 Apr 2006 08:42:44 -0600 Pat McCormick wrote:> Actually WebDNA doesn't use a flat file. That is the case for the =older Typhoon version, but=20>WebDNA, simply because it can have multiple databases open, is no =longer a flat file system.>=20> The difference is that WebDNA doesn't formalize the structure of a db =in any way. You are=20>responsible for define a sku or key field and there are some nice =tools to assist the process,=20>like [cart]. Comparing that with SQL or Access, those products get =more antsy about key fields,=20>and field formats in general. They also enforce the idea of a database =consisting of a=20>collection of tables, which is also confusing nonsense.>=20> The purpose for products like Oracle, SQL and other "databases" is to =encrypt your text so that=20>you need to buy their products to see your text. Web-DNA is the =un-database database. Create=20>your own relationships. All key fields are optional. Structure your =project any way you want,=20>even using virtual databases ([table]), and to make it even better, =keep all the data in plain=20>text so you can x-ray the files at any time using any text tool. Ya =gotta love that!>=20>=20>=20>=20>=20>=20> On Mar 31, 2006, at 2:12 PM, Bess Ho wrote:>=20>> WebDNA is using flat file for storing data. It is not a =20>> relationship database like MySQL. Also once your flat file grow =20>> beyond roughly 2 GB (check with Network Admin to verify the size), =20>> you can't run data very well. The go-around solution is to break =20>> down WebDNA database into smaller chunks for faster performance. =20>> You really need Relationship Database for scaleable application.>>>> -----Original Message----->> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf =Of>> Kenneth Grome>> Sent: Friday, March 31, 2006 4:55 AM>> To: WebDNA Talk>> Subject: Re: Here we go again...>>>>>> On Fri, 31 Mar 2006 07:05:55 -0500, Terry Wilson wrote:>>> ... you never know when you'll be required to start doing something =a>>> certain way; or at some point, an old solution just isn't good =enough>>> or fast enough any longer ...>>>>>> Example:>>>> A client of mine preferred webdna but his searches were too slow, =20>> so he hired me to debug and fix them. His code was fine but the =20>> database files were not configured to optimize webdna's =20>> performance, so I could only recommend two options: (1) =20>> reconfigure the databases (not a good solution because updated data =20>> files came from another source frequently) ... or (2) switch to =20>> MySQL and give that a try ...>>>> I really didn't know if MySQL could handle the task any faster than =20>> webdna and I told him this, but he went for it anyways. He said =20>> webdna hosting cost too much anyways, and since he wasn't committed =20>> to using it on his server anyways (although he enjoyed personally =20>> mocking up web sites because it's east for a non-programmer to use) =20>> he decided to go with PHP and MySQL.>>>> The moment we switched his search times dropped from about 10 =20>> seconds to less than two seconds. I think the reason is two-fold: =20>> (1) he had database files that were too large for webdna to RAM-=20>> cache efficiently, and (2) we were doing nested searches, and =20>> webdna is pretty slow sometimes when using nested searches, =20>> especially with large db files.>>>> The bottom line is that he "outgrew" webdna for use on his server, =20>> and now he's happy again with a faster free solution. I think this =20>> type of situation is going to become more and more common as webdna =20>> continues to be less and less aggressively developed, supported and =20>> marketed.>>>> Sincerely,>> Kenneth Grome>>>> owner@kengrome.com>> kengrome@gmail.com>> www.kengrome.com>>>>>>>>>>>>>> ------------------------------------------------------------->> 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 > digest@talk.smithmicro.com>>> Web Archive of this list is at: http://webdna.smithmicro.com/>>>> ------------------------------------------------------------->> 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 > digest@talk.smithmicro.com>>> Web Archive of this list is at: http://webdna.smithmicro.com/>>>=20>=20> -------------------------------------------------------------> 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/-------------------------------------------------------------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/-------------------------------------------------------------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/
"Bess Ho"
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:
Change in Host? (1999)
[WebDNA] Sendmail BCC bug still exists (2015)
WebStar and CopyFile (2000)
Dates - Search and Sorting (1999)
ShowNext (1997)
WebCat2.0 [format thousands .0f] no go (1997)
Training Tapes Improved (1998)
re: Large databases in WebCat (1997)
sendmail and accented characters (1998)
Superfilous Characters (1998)
Here's how to kill a Butler Database. (1997)
Protect (1997)
Grep and Special Characters (2002)
numlineitems possible cache problem. (2000)
Showing unopened cart (1997)
[AppendFile] problem (WebCat2b13 Mac .acgi) (1997)
[OT] (2002)
[WriteFile] problems (1997)
[WebDNA] How to use attachment with sendmail (2020)
Talk List Suggestions (1997)