Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mysqlpp::BadQuery Crash When using Verif Database #196

Open
hpuhr opened this issue Feb 5, 2021 · 0 comments
Open

mysqlpp::BadQuery Crash When using Verif Database #196

hpuhr opened this issue Feb 5, 2021 · 0 comments
Assignees
Labels

Comments

@hpuhr
Copy link
Owner

hpuhr commented Feb 5, 2021

When using a Verif Database, a user reported the following issue:

"
INFO] TaskManagerWidget: runCurrentTaskSlot: task PostProcessTask
[INFO] TaskManager: runTask: name PostProcessTask
[INFO] PostProcessTask: run: post-processing started
[INFO] PostProcessTask: postProcess: creating jobs
[INFO] DBOActiveDataSourcesDBJob: run: object ADSB
[INFO] PostProcessDBJob: run: creating properties
[INFO] DBOActiveDataSourcesDBJob: run: creating active sensors for dbo ADSB
[INFO] DBOActiveDataSourcesDBJob: run: dbo ADSB active sensors '34'
[INFO] DBOActiveDataSourcesDBJob: run: done (0.348 s).
[INFO] PostProcessTask: postProcessingJobDoneSlot: 6 active jobs
[INFO] DBOMinMaxDBJob: run: start
[INFO] DBOMinMaxDBJob: processTable: getting minimum and maximum of all variables of table sd_ads
[INFO] DBOMinMaxDBJob: run: db postprocessing done (3.277 s).
[INFO] DBOActiveDataSourcesDBJob: run: object Radar
[INFO] PostProcessTask: postProcessingJobDoneSlot: 5 active jobs
[INFO] PostProcessDBJob: run: creating properties
[INFO] DBOActiveDataSourcesDBJob: run: creating active sensors for dbo Radar
[INFO] DBOActiveDataSourcesDBJob: run: dbo Radar active sensors '2,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,27,28,32,41,42'
[INFO] DBOActiveDataSourcesDBJob: run: done (7.876 s).
[INFO] PostProcessTask: postProcessingJobDoneSlot: 4 active jobs
[INFO] DBOMinMaxDBJob: run: start
[INFO] DBOMinMaxDBJob: processTable: getting minimum and maximum of all variables of table sd_radar
[INFO] DBOMinMaxDBJob: run: db postprocessing done (30.133 s).
[INFO] DBOActiveDataSourcesDBJob: run: object Tracker
[INFO] PostProcessDBJob: run: creating properties
[INFO] DBOActiveDataSourcesDBJob: run: creating active sensors for dbo Tracker
[INFO] PostProcessTask: postProcessingJobDoneSlot: 3 active jobs
[INFO] DBOActiveDataSourcesDBJob: run: dbo Tracker active sensors '30,44'
[INFO] DBOActiveDataSourcesDBJob: run: done (0 s).
[INFO] DBOMinMaxDBJob: run: start
[INFO] DBOMinMaxDBJob: processTable: getting minimum and maximum of all variables of table sd_track
[INFO] PostProcessTask: postProcessingJobDoneSlot: 2 active jobs
Qt Concurrent has caught an exception thrown from a worker thread.
This is not supported, exceptions thrown in worker threads must be
caught before control returns to Qt Concurrent.

terminate called after throwing an instance of 'mysqlpp::BadQuery'
what(): Unknown column 'GROUND_BIT' in 'field list'
Aborted (core dumped)
"

This was caused since the user did try to use the DBSchema 'SCDB Extended' with a Verif database, which will not work.
To switch the database schema, please:

  • Open the MySQL database
  • On the left, check the box "Expert Mode"
  • Select the "Manage DB Schema" task, and change the database schema dropdown menu to "SCDB" (not "SCDB Extended"!)

And do not forget to change the DBSchema back to 'SCDB Extended' when using SQLite3 databases.

@hpuhr hpuhr added the wontfix label Feb 5, 2021
@hpuhr hpuhr self-assigned this Feb 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant