Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6

This WebDNA talk-list message is from

2020


It keeps the original formatting.
numero = 115019
interpreted = N
texte = 2647 --Apple-Mail=_D48E1A30-90CE-443F-B444-0DE5A7F0ACB0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Terry Once the AJAX runs, the DB is updated on disk but NOT in RAM.=20 Opening the db file after AJAX has run confirms that the replace has = worked. FLUSHDATABASES is required to flush the DB from RAM and then read it = again to product the correct result in the search. For some reason [FLUSHDATABASES] does not work on the AJAX template. Kind regards Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@plsoftware.com.au > On 19 Feb 2020, at 13:26, talk@webdna.us wrote: >=20 > Hi Stuart, > =20 > Code wise =E2=80=A6you are right =E2=80=A6I see nothing wrong. I = replicated in on our FastCGI WebDNA Win2012R2 boxes =E2=80=A6no issue = works fine and gets saved as well (via jQuery Ajax). > =20 > Will try it on our Linux box later to see if the same occurs as per = yours. > =20 > Here is something you may want to try =E2=80=A6.use = [replacefounditems] > =20 > It may work around the issue in the interim till the mystery is = resolved. Another method is to set up a [table] in your admin-switch.dna = =E2=80=A6collect and store the incoming variables there =E2=80=A6.then = do the [replace] from the stored [table] data to see if that helps. = Incidentally =E2=80=A6having the [table] there will help shorten the = post url string as you can manual have it in the table as default if = needed. > =20 > Just to confirm =E2=80=A6once the Ajax runs the call =E2=80=A6.variable = gets to the landing page =E2=80=A6data is updated in RAM but not in DB. = Could you write a file output after the replace to see if the file = generated has the variable value, since you are saying that the system = is not seeing the variable when called upon by another page and only = after Admin Flush it appears. > =20 > Cheers > Terry Nair > WhatsApp / Mob : +65 9672 9540 > =20 > From: talk@webdna.us >=20 > Sent: Wednesday, February 19, 2020 09:32 AM > To: WebDNA Talk List > > Subject: Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI = version 8.6 > =20 > Hi Terry > =20 > It is hard to work out who sent email to the list now that the = =E2=80=9Cfrom" has changed. > =20 > =20 > The call is very simple, a url with variables.=20 > =20 > =20 > = admin-switch.dna?task=3Dswitch-6&dbid=3D6&dbidname=3DSM-ID&dbname=3Dshippi= ngmethods&dbfield=3DSM-ACTIVE&active=3DT > =20 > =20 > The receiving page is very simple too. >=20 >=20 > [REPLACE db=3D../data/[DBNAME].db&eq[DBIDNAME]datarq=3D[DBID]&max=3D1][!= ] > [/!][DBFIELD]=3D[URL][DBVALUE][/URL][!] > [/!][/REPLACE] > =20 > =20 > The replace is 100% correct in the db file if I open it up, the = problem is that until I manually flush the dbs it is not recognised. > =20 > I have tried putting in [CLOSEDATABASE db=3D../data/[DBNAME].db] or = [COMMITDATABASE db=3D../data/[DBNAME].db] or even [FLUSHDATABASES] with = no resolution. > =20 > It is not the one db, I have another ajax update for another db which = has the same issue. I have not gone through the entire system checking = for others. > =20 > Kind regards > =20 > Stuart Tremain > Pharoah Lane Software > AUSTRALIA > webdna@plsoftware.com.au > =20 > =20 > =20 > =20 > =20 >=20 >=20 >=20 >> On 19 Feb 2020, at 12:11, talk@webdna.us = wrote: >> =20 >> Morning Stuart, >> =20 >> You mentioned =E2=80=9CI have include [FLUSHDATABASES] in the ajax = call=E2=80=9D =E2=80=A6.am I correct to say that you are either doing a = GET or POST Ajax call to a file sitting on the server that has the tags = to execute the flush webdna tag? >> =20 >> If so =E2=80=A6can share the ajax call script and the page called by = it so that I can try to assist you. It is indeed strange that the change = is stored in RAM but not committed into the DB even with all the = settings you mentioned. Regardless =E2=80=A6after the update, the = uncommitted change should still be showing up when called upon by other = pages relying on it. >> =20 >> Cheers TDn >> =20 >> From: talk@webdna.us >=20 >> Sent: Wednesday, February 19, 2020 07:39 AM >> To: WebDNA Talk List > >> Subject: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version = 8.6 >> =20 >> I am having an issue with a couple of dbs. >> =20 >> Permissions are correct 775 >> Ownership is correct www-data:www-data >> =20 >> I am updating the db with an ajax call, I open the db ofter it has = been modified and the mod is there in the db. >> =20 >> The ajax call does a replace on the db. >> =20 >> There is no error reported from the ajax call. >>=20 >>=20 >>=20 >> The WebDNA preference is "Automatically commit databases to disk = after modification" >> =20 >> The problem is that another page on the site is dependant on the new = value. This new value is not being found. >> =20 >> I have include [FLUSHDATABASES] in the ajax call to force the db to = clear however it is still not finding the new value. >> =20 >> If I use the WebDNA admin to [FLUSHDATABASES] then the page finds the = new value. >> =20 >> Any ideas ? >> =20 >> Kind regards >> =20 >> Stuart Tremain >> Pharoah Lane Software >> AUSTRALIA >> webdna@plsoftware.com.au >> =20 >> =20 >> =20 >> =20 >> =20 >>=20 >> =20 >> --------------------------------------------------------- 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 archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us >> --------------------------------------------------------- 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 archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us > =20 > --------------------------------------------------------- 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 archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us = ------------------------------------------------= --------- 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 archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us --Apple-Mail=_D48E1A30-90CE-443F-B444-0DE5A7F0ACB0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi = Terry

Once the AJAX = runs, the DB is updated on disk but NOT in RAM. 
Opening the db file after AJAX has run confirms that the = replace has worked.

FLUSHDATABASES is required to flush the DB from RAM and then = read it again to product the correct result in the search.

For some reason = [FLUSHDATABASES] does not work on the AJAX template.

Kind regards

Stuart Tremain
Pharoah Lane Software
AUSTRALIA







On 19 Feb 2020, at 13:26, talk@webdna.us wrote:

Hi Stuart,
 
Code wise =E2=80=A6you are = right =E2=80=A6I see nothing wrong. I replicated in on our FastCGI = WebDNA Win2012R2 boxes =E2=80=A6no issue works fine and gets saved as = well (via jQuery Ajax).
 
Will try it on our = Linux box later to see if the same occurs as per yours.
 
Here is something you may = want to try =E2=80=A6.use [replacefounditems]
 
It may work around the = issue in the interim till the mystery is resolved. Another method is to = set up a [table] in your admin-switch.dna =E2=80=A6collect and store the = incoming variables there =E2=80=A6.then do the [replace] from the stored = [table] data to see if that helps. Incidentally =E2=80=A6having the = [table] there will help shorten the post url string as you can manual = have it in the table as default if needed.
 
Just to confirm =E2=80=A6onc= e the Ajax runs the call =E2=80=A6.variable gets to the landing page = =E2=80=A6data is updated in RAM but not in DB. Could you write a file = output after the replace to see if the file generated has the variable = value, since you are saying that the system is not seeing the variable = when called upon by another page and only after Admin Flush it = appears.
 
Cheers
Terry Nair
WhatsApp / Mob : +65 9672 9540
 
From: talk@webdna.us <talk@webdna.us> 
Sent: Wednesday, February 19, = 2020 09:32 AM
To: WebDNA Talk List <talk@webdna.us>
Subject: Re: [WebDNA] COMMITDATABASE = in linux unix 64bits FastCGI version 8.6
 
Hi Terry
 
It is hard to work out who sent email to = the  list now that the =E2=80=9Cfrom" has changed.
 
 
The call is very simple, a url with = variables. 
 
 
admin-switch.dna?task=3Dswitch-6&dbid=3D6&dbidname=3DSM= -ID&dbname=3Dshippingmethods&dbfield=3DSM-ACTIVE&active=3DT
 
 
The = receiving page is very simple too.


[REPLACE = db=3D../data/[DBNAME].db&eq[DBIDNAME]datarq=3D[DBID]&max=3D1][!]
          &nb= sp; [/!][DBFIELD]=3D[URL][DBVALUE][/URL][!]
[/!][/REPLACE]
 
 
The replace is 100% correct in the db = file if I open it up, the problem is that until I manually flush the dbs = it is not recognised.
 
I have tried putting = in [CLOSEDATABASE db=3D../data/[DBNAME].db] or [COMMITDATABASE = db=3D../data/[DBNAME].db] or even [FLUSHDATABASES] with no = resolution.
 
It is not the one db, I have another = ajax update for another db which has the same issue. I have not gone = through the entire system checking for others.
 
Kind regards
 
Stuart Tremain
Pharoah Lane Software
AUSTRALIA
 
 
 
 

 



On 19 Feb 2020, at 12:11, talk@webdna.us wrote:
 
Morning Stuart,
 
You mentioned =E2=80=9CI have include [FLUSHDATABASES] in the ajax call=E2=80=9D =E2=80=A6.am I correct to say that you are either = doing a GET or POST Ajax call to a file sitting on the server that has = the tags to execute the flush webdna tag?
 
If so =E2=80=A6can share = the ajax call script and the page called by it so that I can try to = assist you. It is indeed strange that the change is stored in RAM but = not committed into the DB even with all the settings you mentioned. = Regardless =E2=80=A6after the update, the uncommitted change should = still be showing up when called upon by other pages relying on = it.
 
Cheers TDn
 
From: talk@webdna.us <talk@webdna.us> 
Sent: Wednesday, February 19, = 2020 07:39 AM
To: WebDNA Talk List <talk@webdna.us>
Subject: [WebDNA] COMMITDATABASE in = linux unix 64bits FastCGI version 8.6
 
I am having an issue with a couple of dbs.
 
Permissions are correct = 775
Ownership = is correct www-data:www-data
 
I am updating the db with an ajax call, I open the db ofter = it has been modified and the mod is there in the db.
 
The ajax call does a = replace on the db.
 
There is no error reported from the ajax call.



The WebDNA preference is "Automatically commit databases to = disk after modification"
 
The problem is that another page on the site is dependant on = the new value. This new value is not being found.
 
I have include = [FLUSHDATABASES] in the ajax call to force the db to clear however it is = still not finding the new value.
 
If I use the WebDNA = admin to [FLUSHDATABASES] then the page finds the new value.
 
Any ideas ?
 
Kind = regards
 
Stuart Tremain
Pharoah Lane = Software
AUSTRALIA
 
 
 
 

 

 
--------------------------------------------------------- = 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 archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us
--------------------------------------------------------- = 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 archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us
 
--------------------------------------------------------- = 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 archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us
--------------------------------------------------------- = 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 archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

= --------------------------------------------------------- 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 archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail=_D48E1A30-90CE-443F-B444-0DE5A7F0ACB0-- . Associated Messages, from the most recent to the oldest:

    
  1. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Terry Nair" 2020)
  2. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  3. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Terry Nair" 2020)
  4. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Donovan Brooke 2020)
  5. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  6. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Donovan Brooke 2020)
  7. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  8. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Scott @ Itsula" 2020)
  9. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Scott @ Itsula" 2020)
  10. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  11. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Scott @ Itsula" 2020)
  12. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  13. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  14. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Scott @ Itsula" 2020)
  15. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Brian Fries 2020)
  16. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Jym Duane 2020)
  17. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  18. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Terry Nair" 2020)
  19. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  20. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Terry Nair" 2020)
  21. [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
2647 --Apple-Mail=_D48E1A30-90CE-443F-B444-0DE5A7F0ACB0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Terry Once the AJAX runs, the DB is updated on disk but NOT in RAM.=20 Opening the db file after AJAX has run confirms that the replace has = worked. FLUSHDATABASES is required to flush the DB from RAM and then read it = again to product the correct result in the search. For some reason [flushdatabases] does not work on the AJAX template. Kind regards Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@plsoftware.com.au > On 19 Feb 2020, at 13:26, talk@webdna.us wrote: >=20 > Hi Stuart, > =20 > Code wise =E2=80=A6you are right =E2=80=A6I see nothing wrong. I = replicated in on our FastCGI WebDNA Win2012R2 boxes =E2=80=A6no issue = works fine and gets saved as well (via jQuery Ajax). > =20 > Will try it on our Linux box later to see if the same occurs as per = yours. > =20 > Here is something you may want to try =E2=80=A6.use = [replacefounditems] > =20 > It may work around the issue in the interim till the mystery is = resolved. Another method is to set up a [table] in your admin-switch.dna = =E2=80=A6collect and store the incoming variables there =E2=80=A6.then = do the [replace] from the stored [table] data to see if that helps. = Incidentally =E2=80=A6having the [table] there will help shorten the = post url string as you can manual have it in the table as default if = needed. > =20 > Just to confirm =E2=80=A6once the Ajax runs the call =E2=80=A6.variable = gets to the landing page =E2=80=A6data is updated in RAM but not in DB. = Could you write a file output after the replace to see if the file = generated has the variable value, since you are saying that the system = is not seeing the variable when called upon by another page and only = after Admin Flush it appears. > =20 > Cheers > Terry Nair > WhatsApp / Mob : +65 9672 9540 > =20 > From: talk@webdna.us >=20 > Sent: Wednesday, February 19, 2020 09:32 AM > To: WebDNA Talk List > > Subject: Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI = version 8.6 > =20 > Hi Terry > =20 > It is hard to work out who sent email to the list now that the = =E2=80=9Cfrom" has changed. > =20 > =20 > The call is very simple, a url with variables.=20 > =20 > =20 > = admin-switch.dna?task=3Dswitch-6&dbid=3D6&dbidname=3DSM-ID&dbname=3Dshippi= ngmethods&dbfield=3DSM-ACTIVE&active=3DT > =20 > =20 > The receiving page is very simple too. >=20 >=20 > [REPLACE db=3D../data/[DBNAME].db&eq[DBIDNAME]datarq=3D[DBID]&max=3D1][!= ] > [/!][DBFIELD]=3D[url][DBVALUE][/URL][!] > [/!][/REPLACE] > =20 > =20 > The replace is 100% correct in the db file if I open it up, the = problem is that until I manually flush the dbs it is not recognised. > =20 > I have tried putting in [CLOSEDATABASE db=3D../data/[DBNAME].db] or = [COMMITDATABASE db=3D../data/[DBNAME].db] or even [flushdatabases] with = no resolution. > =20 > It is not the one db, I have another ajax update for another db which = has the same issue. I have not gone through the entire system checking = for others. > =20 > Kind regards > =20 > Stuart Tremain > Pharoah Lane Software > AUSTRALIA > webdna@plsoftware.com.au > =20 > =20 > =20 > =20 > =20 >=20 >=20 >=20 >> On 19 Feb 2020, at 12:11, talk@webdna.us = wrote: >> =20 >> Morning Stuart, >> =20 >> You mentioned =E2=80=9CI have include [flushdatabases] in the ajax = call=E2=80=9D =E2=80=A6.am I correct to say that you are either doing a = GET or POST Ajax call to a file sitting on the server that has the tags = to execute the flush webdna tag? >> =20 >> If so =E2=80=A6can share the ajax call script and the page called by = it so that I can try to assist you. It is indeed strange that the change = is stored in RAM but not committed into the DB even with all the = settings you mentioned. Regardless =E2=80=A6after the update, the = uncommitted change should still be showing up when called upon by other = pages relying on it. >> =20 >> Cheers TDn >> =20 >> From: talk@webdna.us >=20 >> Sent: Wednesday, February 19, 2020 07:39 AM >> To: WebDNA Talk List > >> Subject: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version = 8.6 >> =20 >> I am having an issue with a couple of dbs. >> =20 >> Permissions are correct 775 >> Ownership is correct www-data:www-data >> =20 >> I am updating the db with an ajax call, I open the db ofter it has = been modified and the mod is there in the db. >> =20 >> The ajax call does a replace on the db. >> =20 >> There is no error reported from the ajax call. >>=20 >>=20 >>=20 >> The WebDNA preference is "Automatically commit databases to disk = after modification" >> =20 >> The problem is that another page on the site is dependant on the new = value. This new value is not being found. >> =20 >> I have include [flushdatabases] in the ajax call to force the db to = clear however it is still not finding the new value. >> =20 >> If I use the WebDNA admin to [flushdatabases] then the page finds the = new value. >> =20 >> Any ideas ? >> =20 >> Kind regards >> =20 >> Stuart Tremain >> Pharoah Lane Software >> AUSTRALIA >> webdna@plsoftware.com.au >> =20 >> =20 >> =20 >> =20 >> =20 >>=20 >> =20 >> --------------------------------------------------------- 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 archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us >> --------------------------------------------------------- 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 archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us > =20 > --------------------------------------------------------- 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 archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us = ------------------------------------------------= --------- 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 archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us --Apple-Mail=_D48E1A30-90CE-443F-B444-0DE5A7F0ACB0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi = Terry

Once the AJAX = runs, the DB is updated on disk but NOT in RAM. 
Opening the db file after AJAX has run confirms that the = replace has worked.

FLUSHDATABASES is required to flush the DB from RAM and then = read it again to product the correct result in the search.

For some reason = [flushdatabases] does not work on the AJAX template.

Kind regards

Stuart Tremain
Pharoah Lane Software
AUSTRALIA







On 19 Feb 2020, at 13:26, talk@webdna.us wrote:

Hi Stuart,
 
Code wise =E2=80=A6you are = right =E2=80=A6I see nothing wrong. I replicated in on our FastCGI = WebDNA Win2012R2 boxes =E2=80=A6no issue works fine and gets saved as = well (via jQuery Ajax).
 
Will try it on our = Linux box later to see if the same occurs as per yours.
 
Here is something you may = want to try =E2=80=A6.use [replacefounditems]
 
It may work around the = issue in the interim till the mystery is resolved. Another method is to = set up a [table] in your admin-switch.dna =E2=80=A6collect and store the = incoming variables there =E2=80=A6.then do the [replace] from the stored = [table] data to see if that helps. Incidentally =E2=80=A6having the = [table] there will help shorten the post url string as you can manual = have it in the table as default if needed.
 
Just to confirm =E2=80=A6onc= e the Ajax runs the call =E2=80=A6.variable gets to the landing page = =E2=80=A6data is updated in RAM but not in DB. Could you write a file = output after the replace to see if the file generated has the variable = value, since you are saying that the system is not seeing the variable = when called upon by another page and only after Admin Flush it = appears.
 
Cheers
Terry Nair
WhatsApp / Mob : +65 9672 9540
 
From: talk@webdna.us <talk@webdna.us> 
Sent: Wednesday, February 19, = 2020 09:32 AM
To: WebDNA Talk List <talk@webdna.us>
Subject: Re: [WebDNA] COMMITDATABASE = in linux unix 64bits FastCGI version 8.6
 
Hi Terry
 
It is hard to work out who sent email to = the  list now that the =E2=80=9Cfrom" has changed.
 
 
The call is very simple, a url with = variables. 
 
 
admin-switch.dna?task=3Dswitch-6&dbid=3D6&dbidname=3DSM= -ID&dbname=3Dshippingmethods&dbfield=3DSM-ACTIVE&active=3DT
 
 
The = receiving page is very simple too.


[REPLACE = db=3D../data/[DBNAME].db&eq[DBIDNAME]datarq=3D[DBID]&max=3D1][!]
          &nb= sp; [/!][DBFIELD]=3D[url][DBVALUE][/URL][!]
[/!][/REPLACE]
 
 
The replace is 100% correct in the db = file if I open it up, the problem is that until I manually flush the dbs = it is not recognised.
 
I have tried putting = in [CLOSEDATABASE db=3D../data/[DBNAME].db] or [COMMITDATABASE = db=3D../data/[DBNAME].db] or even [flushdatabases] with no = resolution.
 
It is not the one db, I have another = ajax update for another db which has the same issue. I have not gone = through the entire system checking for others.
 
Kind regards
 
Stuart Tremain
Pharoah Lane Software
AUSTRALIA
 
 
 
 

 



On 19 Feb 2020, at 12:11, talk@webdna.us wrote:
 
Morning Stuart,
 
You mentioned =E2=80=9CI have include [flushdatabases] in the ajax call=E2=80=9D =E2=80=A6.am I correct to say that you are either = doing a GET or POST Ajax call to a file sitting on the server that has = the tags to execute the flush webdna tag?
 
If so =E2=80=A6can share = the ajax call script and the page called by it so that I can try to = assist you. It is indeed strange that the change is stored in RAM but = not committed into the DB even with all the settings you mentioned. = Regardless =E2=80=A6after the update, the uncommitted change should = still be showing up when called upon by other pages relying on = it.
 
Cheers TDn
 
From: talk@webdna.us <talk@webdna.us> 
Sent: Wednesday, February 19, = 2020 07:39 AM
To: WebDNA Talk List <talk@webdna.us>
Subject: [WebDNA] COMMITDATABASE in = linux unix 64bits FastCGI version 8.6
 
I am having an issue with a couple of dbs.
 
Permissions are correct = 775
Ownership = is correct www-data:www-data
 
I am updating the db with an ajax call, I open the db ofter = it has been modified and the mod is there in the db.
 
The ajax call does a = replace on the db.
 
There is no error reported from the ajax call.



The WebDNA preference is "Automatically commit databases to = disk after modification"
 
The problem is that another page on the site is dependant on = the new value. This new value is not being found.
 
I have include = [flushdatabases] in the ajax call to force the db to clear however it is = still not finding the new value.
 
If I use the WebDNA = admin to [flushdatabases] then the page finds the new value.
 
Any ideas ?
 
Kind = regards
 
Stuart Tremain
Pharoah Lane = Software
AUSTRALIA
 
 
 
 

 

 
--------------------------------------------------------- = 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 archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us
--------------------------------------------------------- = 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 archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us
 
--------------------------------------------------------- = 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 archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us
--------------------------------------------------------- = 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 archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

= --------------------------------------------------------- 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 archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail=_D48E1A30-90CE-443F-B444-0DE5A7F0ACB0-- . Stuart Tremain

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:

Cart # Starting at 1000 (2000) Follow-Up to: Removing [showif] makes a big difference in speed (1997) WebDNA-Talk Digest mode broken (1997) required fields (1998) Another question (1997) Database monitoring (2005) A few months ago (2001) A little help on e-mail (HELP!!! :-) ) (1998) Search in 2 or more catalogs (1997) Just Testing (1997) Trouble with Netscape (1998) WebCatalog for guestbook ? (1997) Webcat not processed for CACHEd image error pages (1998) [WebDNA] Secure Cookies (2009) [WebDNA] Processor Maxing out (2010) Help! WebCat2 bug (1997) remotely add + sign (1997) Re:2nd WebCatalog2 Feature Request (1996) all records returned. (1997) Banner DNA (1997)