Re: Large databases in WebCat
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 14500
interpreted = N
texte = The SQL-based language is more mature and has more advanced query capabilities. WebCatalog is great for stores and many other applications, but some instances, more complex queries will be required.Another instance would be long reports of huge databases of related tables. Since WebDNA basically re-does the search of a child table each time a record is retrieved and printed (or added to file, etc.), I'm imagining it would get pretty bogged down speed wise. But then WebDNA's approach doesn't get the dreaded outer-join problem.Also, data-validation is a tad easier with a program language like FoxPro than with HTML limitations. But Java and JavaScript are probably changing this. Another big thing is record locking. Multi-user systems have to protect the integrity of their data. If one person checks out some data, they need to be able to lock that data, preventing someone else from modifying it before they are done modifying it. This isn't very important with the web-commerce e-stores here, but would be if inventory amounts were live data and a rush was going on (What, you said you had the Beanie Babies in stock!). (you might be able to simulate this to some degree in WebDNA, but would have to remember to unlock if the user abandons it while locked (this can be a problem in DB databases too -- my husband had his named broadcoast all over the local Home Depot looking for the employee who had his special order record locked and inaccessible))WebDNA is much easier than FoxPro, etc. to learn and implement. It's fast, platform independent, and currently optimized for electronic commerce. The tab-deliminated table structure can be imported into about anything. There's no dreaded ODBC drivers to slow you to a crawl or eliminate platform choice. There's little slow hard-disk access (unless specified).Best of all, Pacific Coast listens to its customers and quickly implements new features that are properly justified (try that with Microsoft!)Sandy Mark Rauterkus wrote: > > > you have to re-think your basic assumptions. Some of those assumptions > >(like SQL is the only answer, and it has to be connected 'live' to the > >web) aren't always the solution. > > OK Grant, (and others); > > When, if ever, would you recomend that a customer go with a SQL DB vs. > Web Catalog? > > I know that this is a very leading and open-ended question, but there you > go. > > -------------- > Mark Rauterkus, Publisher, S.S.S. http://www.sportsurf.net > > mrauterkus@sportsurf.net http://www.SportSurf.Net/FootNotes > > FootNotes: Mac E-book authoring and distribution environment with > built-in multi-media, lan, web, internet and e-mail capabilities. > --------------
Associated Messages, from the most recent to the oldest:
The SQL-based language is more mature and has more advanced query capabilities. WebCatalog is great for stores and many other applications, but some instances, more complex queries will be required.Another instance would be long reports of huge databases of related tables. Since WebDNA basically re-does the search of a child table each time a record is retrieved and printed (or added to file, etc.), I'm imagining it would get pretty bogged down speed wise. But then WebDNA's approach doesn't get the dreaded outer-join problem.Also, data-validation is a tad easier with a program language like FoxPro than with HTML limitations. But Java and JavaScript are probably changing this. Another big thing is record locking. Multi-user systems have to protect the integrity of their data. If one person checks out some data, they need to be able to lock that data, preventing someone else from modifying it before they are done modifying it. This isn't very important with the web-commerce e-stores here, but would be if inventory amounts were live data and a rush was going on (What, you said you had the Beanie Babies in stock!). (you might be able to simulate this to some degree in WebDNA, but would have to remember to unlock if the user abandons it while locked (this can be a problem in DB databases too -- my husband had his named broadcoast all over the local Home Depot looking for the employee who had his special order record locked and inaccessible))WebDNA is much easier than FoxPro, etc. to learn and implement. It's fast, platform independent, and currently optimized for electronic commerce. The tab-deliminated table structure can be imported into about anything. There's no dreaded
ODBC drivers to slow you to a crawl or eliminate platform choice. There's little slow hard-disk access (unless specified).Best of all, Pacific Coast listens to its customers and quickly implements new features that are properly justified (try that with Microsoft!)Sandy Mark Rauterkus wrote: > > > you have to re-think your basic assumptions. Some of those assumptions > >(like SQL is the only answer, and it has to be connected 'live' to the > >web) aren't always the solution. > > OK Grant, (and others); > > When, if ever, would you recomend that a customer go with a SQL DB vs. > Web Catalog? > > I know that this is a very leading and open-ended question, but there you > go. > > -------------- > Mark Rauterkus, Publisher, S.S.S. http://www.sportsurf.net > > mrauterkus@sportsurf.net http://www.SportSurf.Net/FootNotes > > FootNotes: Mac E-book authoring and distribution environment with > built-in multi-media, lan, web, internet and e-mail capabilities. > --------------
Sandra L. Pitner
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:
WC 3.0.1 Mac days_to_date (1998)
Multiple Newcarts (1996)
Re:[ShowIf] and empty fields (1997)
Invoice in another window (1998)
Banner Ad example (Typhoon) and WebCatalog (1997)
Help with [LineItems] in [OrderFile] on ShoppingCart.tpl (2003)
[WebDNA] v7 Stress Test and Strange Behaviour (2012)
greater than or equal to (1997)
WebCatalog can't find database (1997)
Digest Version (2000)
Help with nested search (1998)
Thanks Grant (1997)
Me know logical no need (2002)
test (2000)
Windows XP + Apache 2.0 + WebDNA (2002)
why .HTML pages no processing? (2000)
cookie length (1998)
Dates (1996)
Draft Manual, Tutorial, and more (1997)
Trigger problem (2003)