tab for database operations

[filefolder]

do database operations (e.g. drop all, populate_database_from_sds*, delete_elements, run_query, various admin functions) need a separate tab on the left?

for "run query", a few SQL examples (e.g. delete where station="NAME" between 2019-01-01 and 2020-01-01) would be good as well, but those can be dropped in much later

*this is in seismoloader.py, rest in db.py

[bmotevalli]

@filefolder do we need operations only on the database? I mean if user decides to delete a network or a station should it be only deleted from the DB or we should also consider cleaning up SDS files?

[filefolder]

definitely just the database, shouldn't be any issue for people to delete files out of the SDS manually

primarily just a place to run some SQL would suffice for most of everything, especially if we can supply examples

[bmotevalli]

A dataexplorer tab is added, but after internal meeting we believe it would be better to have more controlled ways of querying. At present, the explorer provides a complete freedom to run any queries, which might not be desirable. Let's discuss this in the next meeting. @filefolder

[filefolder]

sounds good. if we were to leave it in there would definitely have to be a strict warning / advice about backing up one's database. the worst case would really be a user just having to re-sync their archive.

[immotus]

I would be very concerned about deploying this functionality in any hosted solution. If it is only designed to run locally, then it is okay, but if we intend to deploy a shared production version, then I would be reluctant to allow such functionality at all.