Re: Here we go again...
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66689
interpreted = N
texte = Can you use WebDNA database outside WebDNA folder? Are you required to use WebDNA to interect with WebDNA database? How do you see the database relationship? Bess -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Pat McCormick Sent: Saturday, April 01, 2006 6:43 AM To: WebDNA Talk Subject: Re: Here we go again... Actually WebDNA doesn't use a flat file. That is the case for the =20 older Typhoon version, but WebDNA, simply because it can have =20 multiple databases open, is no longer a flat file system. The difference is that WebDNA doesn't formalize the structure of a db =20 in any way. You are responsible for define a sku or key field and =20 there are some nice tools to assist the process, like [cart]. =20 Comparing that with SQL or Access, those products get more antsy =20 about key fields, and field formats in general. They also enforce the =20 idea of a database consisting of a collection of tables, which is =20 also confusing nonsense. The purpose for products like Oracle, SQL and other "databases" is to =20 encrypt your text so that you need to buy their products to see your =20 text. Web-DNA is the un-database database. Create your own =20 relationships. All key fields are optional. Structure your project =20 any way you want, even using virtual databases ([table]), and to make =20 it even better, keep all the data in plain text so you can x-ray the =20 files at any time using any text tool. Ya gotta love that! On Mar 31, 2006, at 2:12 PM, Bess Ho wrote: > 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/ > ------------------------------------------------------------- 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:
Can you use WebDNA database outside WebDNA folder? Are you required to use WebDNA to interect with WebDNA database? How do you see the database relationship? Bess -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Pat McCormick Sent: Saturday, April 01, 2006 6:43 AM To: WebDNA Talk Subject: Re: Here we go again... Actually WebDNA doesn't use a flat file. That is the case for the =20 older Typhoon version, but WebDNA, simply because it can have =20 multiple databases open, is no longer a flat file system. The difference is that WebDNA doesn't formalize the structure of a db =20 in any way. You are responsible for define a sku or key field and =20 there are some nice tools to assist the process, like [cart]. =20 Comparing that with SQL or Access, those products get more antsy =20 about key fields, and field formats in general. They also enforce the =20 idea of a database consisting of a collection of tables, which is =20 also confusing nonsense. The purpose for products like Oracle, SQL and other "databases" is to =20 encrypt your text so that you need to buy their products to see your =20 text. Web-DNA is the un-database database. Create your own =20 relationships. All key fields are optional. Structure your project =20 any way you want, even using virtual databases ([table]), and to make =20 it even better, keep all the data in plain text so you can x-ray the =20 files at any time using any text tool. Ya gotta love that! On Mar 31, 2006, at 2:12 PM, Bess Ho wrote: > 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/ > ------------------------------------------------------------- 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:
I got caught! (2003)
Losing file paths? (1999)
Problem when Inputing text (1999)
(1997)
Separate SSL Server (1997)
Limiting user access to .tmpl files (1997)
Using the new syntax/scoping methods (2000)
Problem (1997)
Re:Searching for ALL / empty form field (1997)
default value from Lookup (1997)
[WebDNA] parsing xml (2010)
Not really WebCat (1997)
PCS Frames (1997)
Not reading code (1997)
Webcatalog and foreign languages (1998)
Help! WebCat2 bug (1997)
Blocking off access (2005)
READFILE command? (1998)
[WebDNA] Installing 7.1.702 on CentOS (2012)
WC2.0 Memory Requirements (1997)