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

Entity Framework New Database Values #91

Open
Patowhiz opened this issue Jun 7, 2018 · 3 comments
Open

Entity Framework New Database Values #91

Patowhiz opened this issue Jun 7, 2018 · 3 comments

Comments

@Patowhiz
Copy link

Patowhiz commented Jun 7, 2018

The entity framework fails to pick new database values that have not been updated through it.

@Patowhiz Patowhiz mentioned this issue Jun 8, 2018
@maxwellfundi
Copy link

@isedwards We have encountered this issue when we for example update the number of wind directions and wind speed via the general settings which should be reflected on to the hourly wind dialog but then even after updating the regkeys table for the speed and direction we have to restart the system for it to pick up the change. What would be your advice on like a way to refresh so that changes not made via EF can be reflected without restarting the system?

@maxwellfundi
Copy link

maxwellfundi commented Jun 8, 2018

This also affects selection of the synoptic hours in hourly and hourly wind -when we update the hourly time selection from the tools> hourly selection , we have to restart the software so that the Enable synoptic hours pick the correct values from that table. @smachua this explains why this did not work actually. I hope @isedwards will advice us on how to handle this issue.

@dannyparsons
Copy link

I get the same issue.

In our DataCall if you replace clsDataConnection.db with New mariadb_climsoft_test_db_v4Entities then you get the correct values from the database without restarting.

So this means that the shared db property in clsDataConnection is not accessing the updated values from the database.

If we make db not shared then that will probably solve the issue but then we would need to create many instances of clsDataConnection (and therefore many instances of mariadb_climsoft_test_db_v4Entities) which is probably not desirable.

@maxwellfundi @Patowhiz have you confirmed that this is only happening for database changes outside of EF? i.e. Have you checked that if you change the form_hourly_time_selection table through EF you don't get this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants