Page 3 of 3

Re: Database Writer "updates" some existing records when option is disabled

Posted: Sun Apr 07, 2019 11:28 pm
by agw
The RTC thing was a long shot :) It wouldn't have explained the incorrect updates, the clock doesn't get involved in the decision as to whether an aircraft gets updated or not (unless you have updates turned on, which you don't). A big leap in the real world clock could cause some temporary weird effects though, there are things that happen if things aren't updated for 10+ seconds etc. so a leap of several days could trigger those effects. I can't imagine how they would affect the online lookup caching though.

If I could get a debugger running on the Pi, and if it's as easy to reproduce on the Pi as you say, then I should be able to see what's happening fairly easily. Unfortunately I don't think it's easy to get a debugger running on the Pi. However I do have a few Pis doing things here, including one running VRS (although I don't want to mess about with that one). I might try putting some trace statements into a test build and see if they can shed some light as to what's happening, whereabouts things are going wrong. Also see whether I can reproduce it as well. My attempts so far have been on Windows. I didn't get a chance to do anything on VRS this weekend but I'll see if I can try it during the week.

Re: Database Writer "updates" some existing records when option is disabled

Posted: Mon May 06, 2019 4:21 pm
by Commander

After I have manually edited the database (in SQLite Expert Personal) and changed the OPERATOR CODES, it will clear the editing as soon as I start the VRS and the current aircraft is in the air.

I have database writer plug-in SETUP to "save online lookups in database".
It is NOT set to "overwrite details on existing aircraft".

The problem is the same as below....

Skibox wrote:
Sat Mar 03, 2018 2:07 pm

"Save Onlne lookups..." enabled
"Overwrite details..." disabled

But still many of my corrected records gets overwritten with the old, faulty data which is coming from the online lookup database.

Op codes disappear, Operator names gets changed back to outdated info.


But i can not understand how to solve the problem in accordance with this answer?
agw wrote:
Tue Mar 12, 2019 12:04 am
The problem was fixed and released last year.

If you are not using the database editor plugin to modify the aircraft records then you need to ensure that the UserString1 is not set to "Missing". The issue, or at least the one that I fixed, was that this field is used as a marker for placeholder aircraft records created from missing online lookups and the database editor plugin wasn't clearing the field when a manual edit was applied.

I have tried to change from (null) to an X in the UserString1 but i still changes back to nothing in the OP Code field.
How can I solve the problem?