Better queryset errors

[hhegre]

Would be good if more queryset error messages reach the user. For instance, in :

.with_column(Column("ged_gte_25","country_month","ged_sb_best_sum_nokgx")

it would be very useful if this results in error messages telling us that "country_month" is not a table in the database and (if the table exists) that "ged_sb_best_sum_nokgx" is not a column in this table.

I understand some error message is produced in the logs, but it would be more convenient if they are visible from the notebook.

[Peder2911]

Hey! This is a really important issue that I have been working towards here: #33

The underlying error handling code for providing better feedback has actually been written already, I just need to document the process and make the backend return useful error messages when appropriate. Thanks for raising this!

[Peder2911]

Handling a lot of the underlying problems here: prio-data/views_queryset_manager#17

[Peder2911]

Remedied by ^, although errors could still probably be made a lot better.