python3 support, fix recreating views when using separate schema in db_table

mypebble / django-pgviews

Fork of django-postgres that focuses on maintaining and improving support for Postgres SQL Views.

The Unlicense

195 stars 41 forks source link

Closed anneFly closed 8 years ago

anneFly commented 8 years ago

We finished up the Python3 compatibility since we needed it to work for us on Python3.
Furthermore, we have the case where we want to create views in a different postgres schema and not the public one (e.g. db_table = 'some_schema_name.some_table_name'). We added a small fix to support this.

scott-w commented 8 years ago

This is really good work guys, thanks for this! Could you update the README with a section explaining how to use the schema feature for us please?

Other than that, I'm happy to merge this and roll a release to PyPI.

anneFly commented 8 years ago

I updated the README and also added tests for a view that uses a separate schema. It felt safer to have this tested as well :)

scott-w commented 8 years ago

Merged this in, thanks for your work :+1:

scott-w commented 8 years ago

@anneFly I've pushed version 0.0.7 to PyPI for you guys. Feel free to open any bugs if you find any issues.