Create views inside an atomic transaction

[caioariede]

With this change we ensure DROP ... CREATE happens inside an atomic transaction, and if any issues happens during the CREATE process, the "old" view is still accessible.

Also, within the transaction, we understand that the view is accessible even during its creation, being replaced only when the new one is available (after commit).

[caioariede]

@tpict hey, thanks for maintaining this amazing package! It is been very helpful for us. Do you mind taking a look on this PR when you get a chance? :)

[tpict]

hi! thanks for the PR, this seems like a sensible addition 😄 I'll take a closer look and get back to you in the next 2-3 days (sorry, super busy at the moment)

[caioariede]

@tpict awesome! One of the tests I did locally, was to add %x to Postgres log_line_prefix and see through the logs the transaction for each statement.

Let me know if you need anything from me.

[tpict]

hi @caioariede, sorry about the delay! merging this in, thanks for the PR 👍

[caioariede]

@tpict thank you!

Do you think this PR is worth it a new version on PyPI? The great benefit of having views being created inside an atomic transaction is that the "old" view is still accessible during recreation.

Releasing this to PyPI would be a tremendous benefit for us to remove workarounds for our codebase, but it totally up to you :)

[tpict]

i'll release a new version this evening since you asked nicely 😉

[caioariede]

Awesome! Thanks :)