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 querycapabilities. WebCatalog is great for stores and many otherapplications, but some instances, more complex queries will be required.Another instance would be long reports of huge databases of relatedtables. Since WebDNA basically re-does the search of a child table eachtime a record is retrieved and printed (or added to file, etc.), I'mimagining it would get pretty bogged down speed wise. But then WebDNA'sapproach doesn't get the dreaded outer-join problem.Also, data-validation is a tad easier with a program language likeFoxPro than with HTML limitations. But Java and JavaScript are probablychanging this. Another big thing is record locking. Multi-user systems have to protectthe integrity of their data. If one person checks out some data, theyneed to be able to lock that data, preventing someone else frommodifying it before they are done modifying it. This isn't veryimportant with the web-commerce e-stores here, but would be if inventoryamounts were live data and a rush was going on (What, you said you hadthe Beanie Babies in stock!). (you might be able to simulate this tosome degree in WebDNA, but would have to remember to unlock if the userabandons it while locked (this can be a problem in DB databases too --my husband had his named broadcoast all over the local Home Depotlooking for the employee who had his special order record locked andinaccessible))WebDNA is much easier than FoxPro, etc. to learn and implement. It'sfast, platform independent, and currently optimized for electroniccommerce. The tab-deliminated table structure can be imported intoabout anything. There's no dreaded ODBC drivers to slow you to a crawlor eliminate platform choice. There's little slow hard-disk access(unless specified).Best of all, Pacific Coast listens to its customers and quicklyimplements new features that are properly justified (try that withMicrosoft!)SandyMark 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 querycapabilities. WebCatalog is great for stores and many otherapplications, but some instances, more complex queries will be required.Another instance would be long reports of huge databases of relatedtables. Since WebDNA basically re-does the search of a child table eachtime a record is retrieved and printed (or added to file, etc.), I'mimagining it would get pretty bogged down speed wise. But then WebDNA'sapproach doesn't get the dreaded outer-join problem.Also, data-validation is a tad easier with a program language likeFoxPro than with HTML limitations. But Java and JavaScript are probablychanging this. Another big thing is record locking. Multi-user systems have to protectthe integrity of their data. If one person checks out some data, theyneed to be able to lock that data, preventing someone else frommodifying it before they are done modifying it. This isn't veryimportant with the web-commerce e-stores here, but would be if inventoryamounts were live data and a rush was going on (What, you said you hadthe Beanie Babies in stock!). (you might be able to simulate this tosome degree in WebDNA, but would have to remember to unlock if the userabandons it while locked (this can be a problem in DB databases too --my husband had his named broadcoast all over the local Home Depotlooking for the employee who had his special order record locked andinaccessible))WebDNA is much easier than FoxPro, etc. to learn and implement. It'sfast, platform independent, and currently optimized for electroniccommerce. The tab-deliminated table structure can be imported intoabout anything. There's no dreaded
ODBC drivers to slow you to a crawlor eliminate platform choice. There's little slow hard-disk access(unless specified).Best of all, Pacific Coast listens to its customers and quicklyimplements new features that are properly justified (try that withMicrosoft!)SandyMark 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:
$adminput doesn't allow [include] files (1997)
Where's Cart Created ? (1997)
WebCat2: multiple currency support (1997)
Tab Charactor (1997)
Single Link browsing (1997)
Nav. 4 probs with cart (1997)
Multiple serial numbers (1997)
missing records (1998)
Rounding question (2002)
[WebDNA] Emailer breaking format (2015)
Need help with emailer- 2 issues (1997)
Calculating Age from DB fields (2003)
Showif -what am I missing??? (1999)
WebCatalog/WebMerchant bug? (1999)
Searching a database... (2003)
[WebDNA] El Capitan (2017)
frames & carts (1997)
simple forum/bboard (2004)
Help name our technology! (1997)
[click][/click] (1999)