Re: flushing databases
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 50113
interpreted = N
texte = As I understand it, [closedatabase] saves and closes the database removing it from memory. It is not accessed again until it is needed. If this is an infrequently used databased, close might be your better option, it's going to get closed due to inactivity eventually anyway.[commitdatabase] saves the database file to disk and sort of refreshes the database in RAM. If you are making a change and then searching that database again immediately afterwards, commitdatabase is your better option.My standard usage is [commitdatabase] after a modification, unless I'm writing to a storage database that won't be used for a while.Form Submit -> [append]/[replace]/[delete] -> [commitdatabase] -> [redirect]-- Matthew C. Bohne Web Developer Sandusky Register 314 W. Market St. Sandusky, OH 44870 419-625-5500 ext. 253 matthewbohne@sanduskyregister.com http://www.sanduskyregister.comOn Wednesday, May 7, 2003 10:13 AM, andy mowrey
wrote: >Nitai, > >I use [COMMITDATABASE db=FileName.db] instead of [CLOSEDATABASE >db=FileName.db]; is close better (more complete) than commit? If so, >what would you use commit for then? > >andy > >> On 7.5.2003 15:57 Uhr, Dave Hurley wrote: >> >>> Forgive what may be a FAQ from a newbie. I'm trying my first database >>> display, which works. But when I modify the database file and the >>> reload the search page, it doesn't reflect the changes to the file. >>> Should I add a trigger to flush databases during such testing (or >>> always) to flush DBs? >> >> If you are in a template doing a replace or append you can either use >> [closedatabase db=mydb.db] >> >> Or if it is just a one-timer then login to the administration of >> WebDNA and >> flush the databases. >> >> Sincerely, >> Nitai Aventaggiato >> CEO >> >> -- >> Tools to energize your business >> Content Management & eBusiness Systems >> >> ComputerOil™ GmbH http://computeroil.com/ >> Unionstrasse 4 info@computeroil.com >> 8032 Zürich/Switzerland >> Tel: +41 (0)43 333 1 555 >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to >> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> > > >------------------------------------------------------------- >This message is sent to you because you are subscribed to > the mailing list . >To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >Web Archive of this list is at: http://webdna.smithmicro.com/ >------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
As I understand it, [closedatabase] saves and closes the database removing it from memory. It is not accessed again until it is needed. If this is an infrequently used databased, close might be your better option, it's going to get closed due to inactivity eventually anyway.[commitdatabase] saves the database file to disk and sort of refreshes the database in RAM. If you are making a change and then searching that database again immediately afterwards, commitdatabase is your better option.My standard usage is [commitdatabase] after a modification, unless I'm writing to a storage database that won't be used for a while.Form Submit -> [append]/[replace]/[delete] -> [commitdatabase] -> [redirect]-- Matthew C. Bohne Web Developer Sandusky Register 314 W. Market St. Sandusky, OH 44870 419-625-5500 ext. 253 matthewbohne@sanduskyregister.com http://www.sanduskyregister.comOn Wednesday, May 7, 2003 10:13 AM, andy mowrey wrote: >Nitai, > >I use [COMMITDATABASE db=FileName.db] instead of [CLOSEDATABASE >db=FileName.db]; is close better (more complete) than commit? If so, >what would you use commit for then? > >andy > >> On 7.5.2003 15:57 Uhr, Dave Hurley wrote: >> >>> Forgive what may be a FAQ from a newbie. I'm trying my first database >>> display, which works. But when I modify the database file and the >>> reload the search page, it doesn't reflect the changes to the file. >>> Should I add a trigger to flush databases during such testing (or >>> always) to flush DBs? >> >> If you are in a template doing a replace or append you can either use >> [closedatabase db=mydb.db] >> >> Or if it is just a one-timer then login to the administration of >> WebDNA and >> flush the databases. >> >> Sincerely, >> Nitai Aventaggiato >> CEO >> >> -- >> Tools to energize your business >> Content Management & eBusiness Systems >> >> ComputerOil™ GmbH http://computeroil.com/ >> Unionstrasse 4 info@computeroil.com >> 8032 Zürich/Switzerland >> Tel: +41 (0)43 333 1 555 >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to >> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> > > >------------------------------------------------------------- >This message is sent to you because you are subscribed to > the mailing list . >To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >Web Archive of this list is at: http://webdna.smithmicro.com/ >------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Matthew Bohne
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:
Script install tgz for WebCat 4.02 (2003)
Smith Micro - no competition (2000)
[TCPconnect].... (2001)
Banners (1997)
Mac Vs WindowsNT (1997)
wierd [cart] action! (1997)
WebCat/Typhoon Status under Windows (1998)
select multiple (1997)
Setting up emailer (1998)
WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997)
Max Record length restated as maybe bug (1997)
2nd WebCatalog2 Feature Request (1996)
Search Engines (2002)
Freeze (2003)
problems with 2 tags shakur (1997)
A question on sub-categories (1997)
Running 2 two WebCatalog.acgi's (1996)
Text variables do not show (1999)
Multiple Users.db Possible? (1997)
Cart passing in URL.. (2004)