Bugs in 2.0.2

[Sentry_e3]

Since Database writer plugin is off, the bug has disappeared! Laurent told me that Active display, which was in use, is causing some troubles (SBS populate didn't....)

For the corrupted files, i'll wait for your advices!

[agw]

Active display, which was in use, is causing some troubles

It is not Active Display that is writing to the database, it is BaseStation.exe. I can see BaseStation's records in your SystemEvents table. It has been writing to this database pretty much continuously since at least 13:38 December 4th 2013 until yesterday morning when the copy was taken.

Despite what you might think you DO have an installation of BaseStation writing to this database somewhere.

Code: Select all

sqlite> select * from SystemEvents order by TimeStamp limit 10;
145774|2013-12-04 13:38:00.371|BaseStation|Client disconnection for 1224
145775|2013-12-04 13:38:00.387|BaseStation|New client connection on localhost for 1224
145776|2013-12-04 13:39:26.965|BaseStation|Client disconnection for 1224
145777|2013-12-04 13:39:26.981|BaseStation|New client connection on localhost for 1224
145778|2013-12-04 13:40:53.184|BaseStation|Client disconnection for 1224
145779|2013-12-04 13:40:53.184|BaseStation|New client connection on localhost for 1224
145780|2013-12-04 13:42:19.590|BaseStation|Client disconnection for 1224
145781|2013-12-04 13:42:19.590|BaseStation|New client connection on localhost for 1224
145782|2013-12-04 13:43:45.996|BaseStation|Client disconnection for 1224
145783|2013-12-04 13:43:45.996|BaseStation|New client connection on localhost for 1224

Code: Select all

sqlite> select * from SystemEvents where SystemEventsID > 916010;
916011|2014-08-22 09:56:52.984|BaseStation|Error (10053) occurred on socket 1128
916012|2014-08-22 09:56:53.031|BaseStation|Client disconnection for 1128
916013|2014-08-22 09:56:53.328|BaseStation|New client connection on localhost for 1128
916014|2014-08-22 09:57:19.375|BaseStation|Locked for 00:00:02
916015|2014-08-22 09:57:23.093|BaseStation|Locked for 00:00:02
916016|2014-08-22 09:57:25.125|BaseStation|Locked for 00:00:02
916017|2014-08-22 09:57:28.203|BaseStation|Locked for 00:00:03
916018|2014-08-22 09:57:31.187|BaseStation|Locked for 00:00:02
916019|2014-08-22 09:57:34.000|BaseStation|Locked for 00:00:02
916020|2014-08-22 09:57:37.156|BaseStation|Locked for 00:00:03
916021|2014-08-22 09:57:42.953|BaseStation|Locked for 00:00:05
sqlite>

I imagine your database is actually alright, the reason the copy you sent to me was corrupt is probably because BaseStation was still writing to it when you were zipping it up.

[Sentry_e3]

Yes basestation is running because, if i've well understood Laurent, it is needed to use active display

do you think it could be the cause of the bug?

[agw]

It's not really a bug But yes, the reason why you have two flight records for each flight in the database is because you have (or had) two programs writing flights to the database. The download page and the installer for the database writer plugin warns people not to install it if they're running BaseStation. That warning is there because BaseStation is already doing all of the things that the plugin does; the plugin is a replacement for BaseStation's database functionality. If you run the plugin and BaseStation at the same time, and on the same database, you end up with duplicate aircraft and flight records.

[Sentry_e3]

Andrew, the .sqb database file is again worrying me... i've sent you the file by PM, if you can check please

Thanks!