⊠double post AGAIN âŠ
race conditions ⊠LOL
⊠double post AGAIN âŠ
race conditions ⊠LOL
Yes, and that is exactly what I am implying.
Maybe, but that could manifest itself as a race condition.
I will not deny that Update Type:Increase appears to be broken when you update a value then subsequently read it.
But even that ^ could be a race. It doesnât mean the value wasnât updated, it just means the subsequent READ was too fast.
Or are you claiming otherwise? Are you saying that Increase is broken? How do you know for sure?
I think I did yesterday on Server (not RDP) so, i donât think multi session too. It just pure Update Type Increase
I think the value we pass to the
Update Program Setting
action is not read from DB.
No matter if Increase
or Update
type.
While I think that what you mean is:
Update Setting
here impossible to have a race condition
Tagged
maybe race condition, the value is maybe not updated yet, which - if the actions are executed in order - would make Ms SQL server useless.
I know for a fact I use this method with 3 terminals all windows tablets running sambapos and connected to database via connection string all Wi-Fi connected. Never once had it done this. I still think itâs unique to the terminal setup your using. Iâm not saying itâs not a bug it certainly may be.
The event I use though is ticket created
It wouldnât hardly ever be read from the DB. Increase we pass â1â, Update we pass âwhateverâ - it could be a value read from the DB or it could be the word âblahâ.
For Increase we pass:
The Setting Name is the Name in the ProgramSettingValues
Table.
So if using Setting Type Increase
in this blackbox
Of course we have to expect that it will take the current value of the name and it will take it from ProgramSettingValues
table; add Setting value (1) and Update that table.[quote=âQMcKay, post:157, topic:15062â]
Update we pass âwhateverâ
[/quote]
That whatever must be read from DB.
I get what youâre saying now.
Are you implying it is not reading the Value from the DB for the associated Setting NAME? Or that it is not updating it (when using Increase Update Type).
That might be the case but I donât thing so, I think the value we use to tag; to update; (not to increase) is not read from db, it is an independant variable for each SambaPOS instances.
That value is related to {SETTING:SerialNumber}
I might be wrong but that is what I feel.
OK here is the test:
Manually write data to database
Click Test
I click Test Few More
Manually write data to database (Reset To 0 and 100)
Click Test
Before I was using Increase but I was told to use Update instead.
Increase is different:
The function is supposed to read itself the db, while in Update we give that function the value we think we read from DB.
I also had problem (not exactely the same, I had soemtimes 3 times the same number) but that problem was maybe related to TAG and not Update Program Setting with Increase.
Good test. Looks like Update Type:Increase is broken. Looks like it is cached, and not read from DB.
What syntax are you using? {:X}, or {SETTING:X}, or {GLOBAL SETTING:X}
?
Nice test.
However I have it wrong with Update also using {GLOBAL SETTING:UpdateType}
Could you try?
Using {SETTING:X}
can you try with GLOBAL?
Unbelievable we got another bug `{GLOBAL SETTING:X}â = {:X}. So, change it back to {SETTING:X} You should be fine now.
EDIT: GLOBAL read from cache in âBeforeâ but read from database in âAfterâ. It seem it doesnât know the value was update (I manually change database) so, it use local value but after Update Program Setting Action it read from database. @QMcKay
actually I have it setup now with Update and I give the {REPORT SQL} value.
I havenât had double today, I think I will stick with it until the patch.
168 posts later and we uncovered 2 bugs. LOL.
Good work Team!
was this fixed as im getting same issue.
Mine is set to {GLOBAL SETTING:ORDERNUMBER}
What shall i change it to?