Re:2nd WebCatalog2 Feature Request

This WebDNA talk-list message is from

1996


It keeps the original formatting.
numero = 10136
interpreted = N
texte = At 5:32 PM -0800 on 12/7/96, Grant Hulbert wrote: > OK, so now WebCatalog2 can open as many databases as you like, with any >>fieldnames you like.Thank You.. Thank You.. Thank You... > This also means you must now specify the database name whenever you use a >command, such as WebCatalog.acgi$search?db=Catalog.txt&template=xxx >This is getting very similar to Cold Fusion. I think these calls are more than acceptable in order to gain multiple databases. This is a very small price to pay. > Now 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. >Just do it the new way. This should save development time as well as bug smashing. It also eliminates the possibility of some major problems for webmasters who forget to put it in a document.> 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. >Most webmasters only have a few pages to change since in only supported one database in the past. Even if they used work arounds to get more info in one database the changes should be minimal.> 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!Can't wait! Any idea when a beta is slated? What will be the upgrade policy or has it been determined yet? Todd ____________M_E_D_I_A_S_T_O_R_M_______________Todd Mathews mailto:todd@mediastorm.net http://www.mediastorm.net ______________________________________________ Associated Messages, from the most recent to the oldest:

    
  1. Re:2nd WebCatalog2 Feature Request (Todd Mathews 1996)
  2. Re:2nd WebCatalog2 Feature Request (matt@papersite.com (Matthew Steele) 1996)
  3. Re:2nd WebCatalog2 Feature Request (Grant Hulbert 1996)
  4. Re:2nd WebCatalog2 Feature Request (Grant Hulbert 1996)
  5. Re:2nd WebCatalog2 Feature Request (Jim Shaughnessy 1996)
  6. Re:2nd WebCatalog2 Feature Request (Jim Shaughnessy 1996)
  7. Re:2nd WebCatalog2 Feature Request (Grant Hulbert 1996)
  8. Re:2nd WebCatalog2 Feature Request (Todd Mathews 1996)
At 5:32 PM -0800 on 12/7/96, Grant Hulbert wrote: > OK, so now WebCatalog2 can open as many databases as you like, with any >>fieldnames you like.Thank You.. Thank You.. Thank You... > This also means you must now specify the database name whenever you use a >command, such as WebCatalog.acgi$search?db=Catalog.txt&template=xxx >This is getting very similar to Cold Fusion. I think these calls are more than acceptable in order to gain multiple databases. This is a very small price to pay. > Now 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. >Just do it the new way. This should save development time as well as bug smashing. It also eliminates the possibility of some major problems for webmasters who forget to put it in a document.> 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. >Most webmasters only have a few pages to change since in only supported one database in the past. Even if they used work arounds to get more info in one database the changes should be minimal.> 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!Can't wait! Any idea when a beta is slated? What will be the upgrade policy or has it been determined yet? Todd ____________M_E_D_I_A_S_T_O_R_M_______________Todd Mathews mailto:todd@mediastorm.net http://www.mediastorm.net ______________________________________________ Todd Mathews

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:

Date format question (1998) More to Expire (1998) Slow applescript context ... (2000) multiple search commands (1997) Generating Report Totals (1997) [BoldWords] WebCat.acgib15Mac (1997) Changes to the List (1997) Duplicates (1998) Thanks Grant (1997) Some Questions (1997) file browser. (2002) CERT Advisory on malicious scripts (2000) Problems appending to database (1997) Here we go again... was: DDEConnect not working (2006) wish list (2002) Environment Variables (2000) Shipcost lookup? (1997) WebCat2 beta 11 - new prefs ... (1997) [WriteFile] problems (1997) Sort Order on a page search (1997)