Using rawSQL to update a table and then a Flush - the table is updated but the client is not. It is updated when the Client is closed and reopened - but I cant see where there is anything wrong with this SQL ?
I’ve tried an updateUI both as a function call in the form in question from the form where this SQL is run - and also on the form where its run. I assumed the flush would update all client forms?
Here is the code I’m using:
var setFabricQRAIntQuery = "UPDATE fabric_condition SET fc_qra_int = " + vFrr + " where cc_id = " + currentCC
var setFabricIntFlag = plugins.rawSQL.executeSQL("tci_test","fabric_condition",setFabricQRAIntQuery)
plugins.rawSQL.flushAllClientsCache("tci_test","fabric_condition")
I’m sure I’ve missed something so any feedback welcome.
Can you post a small sample solution? Is the data that the client shows in a normal foundset or processed somehow?
executeSQL and flushAllClientsCache should be enough…
Andrei Costescu:
Can you post a small sample solution? Is the data that the client shows in a normal foundset or processed somehow?
executeSQL and flushAllClientsCache should be enough…
Andrei - there is no unusual processing going on there - there are several functions called on record selection but nothing onerous at all and nothing that should influence this. I tried a relookup() too, to no avail.
It seems the broadcast is not working. It is fine after a close and reopen of the client though…?
Not sure I can split this piece out of the solution. Can you confirm this is not an issue in your test environment please (were using MySQL).
Andrei Costescu:
This is indeed reproducible with beta 4, but not with latest build.
So please tell me if you still see it when next build becomes available.
WOW - Andrei - thats gona be a bitch in all testing - serves us right for using beta I suppose!
When do you anticipate the next build being available? Obviously we use the flush everywhere we we use rawSQL?
I’ve worked around this one for the moment but it means running relations on an onRecordeSelection which is where our speed issues came from in the first place, so waiting with bated breath for the next release.
Andrei said it was reproducible in beta4 but not in their latest build. So it was never a specific fix (something has changed alright).
So you can assume the ‘fix’ is indeed included (if not then in the mean time they will have broken again what they fixed, who knows )