Re: Same Database needed on two machines
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 41019
interpreted = N
texte = >On master site, create a page that simply returns the contents of >the database, verbatim - just [include file=the.db]. > >On slave site, create a trigger that does a [tcpconnect] to the >above page on the master site, then replaces the database with the >new data (closedatabase, then writefile). Have the trigger fire as >often as you like.Don't forget to flush the db to disk on the master immediately before you include the db file, or it may not have all the current RAM-cached data in it. Unless of course your prefs on the master are set to always write all db changes to disk, in which case you shouldn't have to flush to disk again before including the db file on the master ... Sincerely, Kenneth Grome------------------------------------------------------------- Kenneth Grome & Associates US-Asian Business Specialists Philippine Business Office +63 (32) 255-6921 Primary Email Address owner@kengrome.com Alternate Email Address kengrome@webdna.net -------------------------------------------------------------------------------------------------------------------------- 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://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>On master site, create a page that simply returns the contents of >the database, verbatim - just [include file=the.db]. > >On slave site, create a trigger that does a [tcpconnect] to the >above page on the master site, then replaces the database with the >new data (closedatabase, then writefile). Have the trigger fire as >often as you like.Don't forget to flush the db to disk on the master immediately before you include the db file, or it may not have all the current RAM-cached data in it. Unless of course your prefs on the master are set to always write all db changes to disk, in which case you shouldn't have to flush to disk again before including the db file on the master ... Sincerely, Kenneth Grome------------------------------------------------------------- Kenneth Grome & Associates US-Asian Business Specialists Philippine Business Office +63 (32) 255-6921 Primary Email Address owner@kengrome.com Alternate Email Address kengrome@webdna.net -------------------------------------------------------------------------------------------------------------------------- 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://search.smithmicro.com/
Kenneth Grome
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:
[isfile] ? (1997)
Error handling for accountNum (1997)
Summing fields (1997)
[WebDNA] Dynamic vertical columns (2008)
RePost: NAT and the CART (1999)
[WebDNA] Set a cookie via setmimeheader? (2014)
WebCatalog NT beta 18 now available (1997)
Correlating the record found with the fieldname (2000)
Understanding texta (1997)
[quantity] and quantity[lineindex] (2000)
[WebDNA] Webdna in France (2013)
Shownext! (1998)
how do you and/or in a search? (1997)
First postarg not taking in $Commands (1997)
Emailer setup (1997)
Checking Out! (1999)
user flush db (2002)
[WebDNA] TCPCONNECT & Timeout (2015)
Help! WebCat2 bug (1997)
Multi-processor Mac info ... (1997)