stop creating tables for views and instead create view for them

[dethrophes]

I'm neither a python nor SQL person. Having said that I find it a bit weird that currently the script is creating a real table for all the views and then populating the views with the data. Which much be exploding the db size, if you use views in sqlite3?

So here I added a hacky approach to instead just create a view for the views.

Not saying this is finished, just providing for feedback. It seems to work at least for me in my limited testing.

Cheers.

[techouse]

The thought of supporting views never crossed my mind. It will sure be good addition.

Please make sure to add unit tests for this.

[techouse]

@dethrophes any more progress on this?