2nd WebCatalog2 Feature Request

This WebDNA talk-list message is from

1996


It keeps the original formatting.
numero = 10135
interpreted = N
texte = OK, so now WebCatalog2 can open as many databases as you like, with any fieldnames you like. How important is backwards-compatibility? We're doing our best to maintain a clean upgrade path, but you will definitely need to change your template files a little bit when you move to WebCatalog2. Even more changes are necessary for the plugin version.The way it works now, you must modify your Catalog.txt file so that the first line contains the fieldnames sku title description ...etcThis also means you must now specify the database name whenever you use a command, such as WebCatalog.acgi$search?db=Catalog.txt&template=xxxNow I could hack in some code that assumes if you don't specify a database, then it should look for a file called Catalog.txt and assume it has the old 27 fixed fields in it. But I don't like this because I'd rather have error-checking so that if you forget to specify a database it can say Sorry, the SEARCH command requires that you specify a database rather than just quietly assuming you _meant_ to use an old-style Catalog.txt file.Personally I don't think it's too hard for webmasters to add that first line of fieldnames, and I'd much rather keep the code clean, fast and small. And I also like the new method of explicitly specifying the database you plan to use, rather than having some hidden assumptions that create tech support nightmares.Oh, well, these are the problems we knew we'd face as we generalized the database code more. Wait til you see how you get the price information into the shopping cart!Grant Hulbert, V.P. Engineering | Tools for WebWarriors Pacific Coast Software | WebCatalog, WebCommerce Solution 11770 Bernardo Plaza Court, #462 | SiteEdit, SiteCheck, PhotoMill San Diego, CA 92128 | 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

    
  1. Re: 2nd WebCatalog2 Feature Request (herrera@tcimet.net (College Shopping Network) 1996)
  2. Re[3]: 2nd WebCatalog2 Feature Request (John Peacock 1996)
  3. Re: 2nd WebCatalog2 Feature Request (GL 1996)
  4. Re[2]: 2nd WebCatalog2 Feature Request (Grant Hulbert 1996)
  5. Re[2]: 2nd WebCatalog2 Feature Request (John Peacock 1996)
  6. Re:2nd WebCatalog2 Feature Request (Todd Mathews 1996)
  7. Re:2nd WebCatalog2 Feature Request (matt@papersite.com (Matthew Steele) 1996)
  8. Re: 2nd WebCatalog2 Feature Request (matt@papersite.com (Matthew Steele) 1996)
  9. Re:2nd WebCatalog2 Feature Request (Grant Hulbert 1996)
  10. Re:2nd WebCatalog2 Feature Request (Grant Hulbert 1996)
  11. Re:2nd WebCatalog2 Feature Request (Jim Shaughnessy 1996)
  12. Re:2nd WebCatalog2 Feature Request (Jim Shaughnessy 1996)
  13. RE: 2nd WebCatalog2 Feature Request (Jim Shaughnessy 1996)
  14. Re:2nd WebCatalog2 Feature Request (Grant Hulbert 1996)
  15. Re:2nd WebCatalog2 Feature Request (Todd Mathews 1996)
  16. 2nd WebCatalog2 Feature Request (Grant Hulbert 1996)
OK, so now WebCatalog2 can open as many databases as you like, with any fieldnames you like. How important is backwards-compatibility? We're doing our best to maintain a clean upgrade path, but you will definitely need to change your template files a little bit when you move to WebCatalog2. Even more changes are necessary for the plugin version.The way it works now, you must modify your Catalog.txt file so that the first line contains the fieldnames sku title description ...etcThis also means you must now specify the database name whenever you use a command, such as WebCatalog.acgi$search?db=Catalog.txt&template=xxxNow I could hack in some code that assumes if you don't specify a database, then it should look for a file called Catalog.txt and assume it has the old 27 fixed fields in it. But I don't like this because I'd rather have error-checking so that if you forget to specify a database it can say Sorry, the SEARCH command requires that you specify a database rather than just quietly assuming you _meant_ to use an old-style Catalog.txt file.Personally I don't think it's too hard for webmasters to add that first line of fieldnames, and I'd much rather keep the code clean, fast and small. And I also like the new method of explicitly specifying the database you plan to use, rather than having some hidden assumptions that create tech support nightmares.Oh, well, these are the problems we knew we'd face as we generalized the database code more. Wait til you see how you get the price information into the shopping cart!Grant Hulbert, V.P. Engineering | Tools for WebWarriors Pacific Coast Software | WebCatalog, WebCommerce Solution 11770 Bernardo Plaza Court, #462 | SiteEdit, SiteCheck, PhotoMill San Diego, CA 92128 | 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Grant Hulbert

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:

Redirect (2003) Re:E-Mailer (WebCatb15acgiMac) (1997) Database Advice (1996) FW: Shipping calculations (1997) Formulas.db / Quantity Discount problem (1998) Sorting error (1997) [delete] problem (1997) Re:No Data (1997) Re:quit command on NT (1997) Configuring E-mail (1997) syntax question, not in online refernce (1997) POST Datamissing? (1998) PCS Customer submissions ? (1997) [writefile] (1997) [WebDNA] Math Date issue (2009) [OT] Movie (2002) maybe even an easier plan to satisfy need for solid tech support? (2000) WebCatalog can't find database (1997) Show items based on login Password (2003) RAM variables (1997)