Re: [WebDNA] Is the AutoCommit preference still supported?

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105329
interpreted = N
texte = --Apple-Mail-29--238920891 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Thanks, Stuart, but I'm afraid you missed my point, which is this: Even though AutoCommit is disabled in preferences, the database is still = being written to disk after every single Append context. Brian Fries BrainScan Software On Jun 14, 2010, at 5:22 PM, Stuart Tremain wrote: > Brian >=20 > The data will go into the db but the db will not be written to the HD = - if you have a crash then the data is lost. >=20 > Try putting this at the end of the page to ensure that your data is = written to disk. >=20 > [COMMITDATABASE db=3DFileName] >=20 > Putting [COMMITDATABASE db=3DFileName] in your template causes the = specified database file (or full path) to be written but not closed (so = it will remain in RAM). This is only needed for special cases where you = want to be absolutely certain that a database has been written to disk. >=20 >=20 >=20 > Regards >=20 > Stuart Tremain > IDFK Web Developments > AUSTRALIA > webdna@idfk.com.au >=20 >=20 >=20 >=20 > On 15/06/2010, at 10:16 AM, Brian Fries wrote: >=20 >> I've been playing with the AutoCommit setting fro my databases. = Historically, I've always kept this on to ensure the integrity of my = data. However, I have an application now that really needs all the speed = it can get, and I'd like to disable AutoCommit. >>=20 >> When I turn off this setting, the databases are still getting written = to disk after every Append. This is with a simple loop that generates = data and appends it to a database. Each time through the loop, I use = [fileinfo] to check the size of the database, and it increases every = time. >>=20 >> OS X Server, WebDNA 6.1 >>=20 >> Brian Fries >> BrainScan Software >>=20 >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> old archives: http://dev.webdna.us/TalkListArchive/ >> Bug Reporting: = http://forum.webdna.us/eucabb.html?page=3Dtopics&category(8 >=20 --Apple-Mail-29--238920891 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Thanks, Stuart, but I'm afraid you missed my point, which is = this:

Even though AutoCommit is disabled in = preferences, the database is still being written to disk after every = single Append context.

Brian = Fries
BrainScan Software

On Jun 14, 2010, at 5:22 PM, Stuart Tremain = wrote:

Brian

The data will go into the db but the db will = not be written to the HD - if you have a crash then the data is = lost.

Try putting this at the end of the page = to ensure that your data is written to = disk.

[COMMITDATABASE db=3DFileName]

Putting = [COMMITDATABASE db=3DFileName] in your template causes the specified = database file (or full path) to be written but not closed (so it will = remain in RAM). This is only needed for special cases where you want to = be absolutely certain that a database has been written to = disk.



Regards

Stuart = Tremain
IDFK Web Developments
AUSTRALIA




On 15/06/2010, at 10:16 AM, Brian Fries wrote:

I've = been playing with the AutoCommit setting fro my databases. Historically, = I've always kept this on to ensure the integrity of my data. However, I = have an application now that really needs all the speed it can get, and = I'd like to disable AutoCommit.

When I turn off this setting, the = databases are still getting written to disk after every Append. This is = with a simple loop that generates data and appends it to a database. = Each time through the loop, I use [fileinfo] to check the size of the = database, and it increases every time.

OS X Server, WebDNA = 6.1

Brian Fries
BrainScan = Software


------------------------------------------------------= ---
This message is sent to you because you are subscribed to
the = mailing list <talk@webdna.us>.
To = unsubscribe, E-mail to: <talk-leave@webdna.us>
archi= ves: http://mail.webdna.us/l= ist/talk@webdna.us
old archives: http://dev.webdna.us/TalkLi= stArchive/
Bug Reporting: htt= p://forum.webdna.us/eucabb.html?page=3Dtopics&category(8
=


= --Apple-Mail-29--238920891-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Is the AutoCommit preference still supported? (Donovan Brooke 2010)
  2. Re: [WebDNA] Is the AutoCommit preference still supported? (Govinda 2010)
  3. Re: [WebDNA] Is the AutoCommit preference still supported? (Brian Fries 2010)
  4. Re: [WebDNA] Is the AutoCommit preference still supported? (Donovan Brooke 2010)
  5. Re: [WebDNA] Is the AutoCommit preference still supported? (Stuart Tremain 2010)
  6. Re: [WebDNA] Is the AutoCommit preference still supported? (Brian Fries 2010)
  7. Re: [WebDNA] Is the AutoCommit preference still supported? (Stuart Tremain 2010)
  8. [WebDNA] Is the AutoCommit preference still supported? (Brian Fries 2010)
--Apple-Mail-29--238920891 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Thanks, Stuart, but I'm afraid you missed my point, which is this: Even though AutoCommit is disabled in preferences, the database is still = being written to disk after every single Append context. Brian Fries BrainScan Software On Jun 14, 2010, at 5:22 PM, Stuart Tremain wrote: > Brian >=20 > The data will go into the db but the db will not be written to the HD = - if you have a crash then the data is lost. >=20 > Try putting this at the end of the page to ensure that your data is = written to disk. >=20 > [COMMITDATABASE db=3DFileName] >=20 > Putting [COMMITDATABASE db=3DFileName] in your template causes the = specified database file (or full path) to be written but not closed (so = it will remain in RAM). This is only needed for special cases where you = want to be absolutely certain that a database has been written to disk. >=20 >=20 >=20 > Regards >=20 > Stuart Tremain > IDFK Web Developments > AUSTRALIA > webdna@idfk.com.au >=20 >=20 >=20 >=20 > On 15/06/2010, at 10:16 AM, Brian Fries wrote: >=20 >> I've been playing with the AutoCommit setting fro my databases. = Historically, I've always kept this on to ensure the integrity of my = data. However, I have an application now that really needs all the speed = it can get, and I'd like to disable AutoCommit. >>=20 >> When I turn off this setting, the databases are still getting written = to disk after every Append. This is with a simple loop that generates = data and appends it to a database. Each time through the loop, I use = [fileinfo] to check the size of the database, and it increases every = time. >>=20 >> OS X Server, WebDNA 6.1 >>=20 >> Brian Fries >> BrainScan Software >>=20 >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> old archives: http://dev.webdna.us/TalkListArchive/ >> Bug Reporting: = http://forum.webdna.us/eucabb.html?page=3Dtopics&category(8 >=20 --Apple-Mail-29--238920891 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Thanks, Stuart, but I'm afraid you missed my point, which is = this:

Even though AutoCommit is disabled in = preferences, the database is still being written to disk after every = single Append context.

Brian = Fries
BrainScan Software

On Jun 14, 2010, at 5:22 PM, Stuart Tremain = wrote:

Brian

The data will go into the db but the db will = not be written to the HD - if you have a crash then the data is = lost.

Try putting this at the end of the page = to ensure that your data is written to = disk.

[COMMITDATABASE db=3DFileName]

Putting = [COMMITDATABASE db=3DFileName] in your template causes the specified = database file (or full path) to be written but not closed (so it will = remain in RAM). This is only needed for special cases where you want to = be absolutely certain that a database has been written to = disk.



Regards

Stuart = Tremain
IDFK Web Developments
AUSTRALIA




On 15/06/2010, at 10:16 AM, Brian Fries wrote:

I've = been playing with the AutoCommit setting fro my databases. Historically, = I've always kept this on to ensure the integrity of my data. However, I = have an application now that really needs all the speed it can get, and = I'd like to disable AutoCommit.

When I turn off this setting, the = databases are still getting written to disk after every Append. This is = with a simple loop that generates data and appends it to a database. = Each time through the loop, I use [fileinfo] to check the size of the = database, and it increases every time.

OS X Server, WebDNA = 6.1

Brian Fries
BrainScan = Software


------------------------------------------------------= ---
This message is sent to you because you are subscribed to
the = mailing list <talk@webdna.us>.
To = unsubscribe, E-mail to: <talk-leave@webdna.us>
archi= ves: http://mail.webdna.us/l= ist/talk@webdna.us
old archives: http://dev.webdna.us/TalkLi= stArchive/
Bug Reporting: htt= p://forum.webdna.us/eucabb.html?page=3Dtopics&category(8
=


= --Apple-Mail-29--238920891-- Brian Fries

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:

Extended [ConvertChars] (1997) could someone please try this - it's very quick and easy (2000) WebCat2final1 crashes (1997) type 2 errors with ssl server (1997) How do I specify a & character in Grep? (2000) Include a big block of text (1997) [WebDNA] exclusivelock (2011) Text data with spaces in them... (1997) Making WebCatalog run as www (2006) 4.5 -> 5, Any issues? (2004) Switching to Linux (2000) [OT] DOD (2002) WebDNA-Talk Digest mode broken (1997) [WebDNA] SMTP sendmail error (2015) Multiple prices (1997) Site Search Concepts (2003) [UPPERCASE] (1997) Email within tmpl ? (1997) Logging purchases (1997) WebCat2b13MacPlugin - nested [xxx] contexts (1997)