Database Updates

This WebDNA talk-list message is from

1997

It keeps the original formatting. numero = 13264
interpreted = N
texte = I posted a related message about this last week. The single answer I got didnot quench my thirst for a better solution.I have enabled several store fronts with the WebCatalog acgi. I now want tofigure out an easy means of updating the various catalog.txt database files. Most clients will be maintaining these in locally operated database files andexporting updates to me. I will then use Timbuktu to place them on the server. However, it seems thatthe only way I can do this is to effectively close and update EVERY databasefile that WebCatalog has opened via the WebCatalog admin interface. Is there not a better way to close a single database and replace it with anewer version without affecting over a dozen other database files?Also, I seem to recall some discussion that the acgi version was not takingmanually entered updates. I remember one client trying to manually update theads.db and any new items he entered did not show up. Is this a known problem? Is there something special that has to be done inorder to get WebCatalog to note that a change to the RAM-based file has beenmade by a manually entered item?John Benn, PetsForum Group Associated Messages, from the most recent to the oldest:

Re: Database Updates (Kenneth Grome 1997)
Re: Database Updates (grichter@panavise.com (Gary Richter) 1997)
Database Updates (John Benn/PetsForum Grp <76703.4256@CompuServe.COM> 1997)
Re: Database Updates (Kenneth Grome 1997)
Database Updates (John Benn/PetsForum Grp <76703.4256@CompuServe.COM> 1997)

I posted a related message about this last week. The single answer I got didnot quench my thirst for a better solution.I have enabled several store fronts with the WebCatalog acgi. I now want tofigure out an easy means of updating the various catalog.txt database files. Most clients will be maintaining these in locally operated database files andexporting updates to me. I will then use Timbuktu to place them on the server. However, it seems thatthe only way I can do this is to effectively close and update EVERY databasefile that WebCatalog has opened via the WebCatalog admin interface. Is there not a better way to close a single database and replace it with anewer version without affecting over a dozen other database files?Also, I seem to recall some discussion that the acgi version was not takingmanually entered updates. I remember one client trying to manually update theads.db and any new items he entered did not show up. Is this a known problem? Is there something special that has to be done inorder to get WebCatalog to note that a change to the RAM-based file has beenmade by a manually entered item?John Benn, PetsForum Group John Benn/PetsForum Grp <76703.4256@CompuServe.COM>

DOWNLOAD WEBDNA NOW!

Database Updates

1997

Top Articles:

Related Readings: