Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Orm.read_only #17

Closed
Jaymon opened this issue Dec 12, 2015 · 2 comments
Closed

Orm.read_only #17

Jaymon opened this issue Dec 12, 2015 · 2 comments

Comments

@Jaymon
Copy link
Owner

Jaymon commented Dec 12, 2015

if you set this to True on a prom.Orm instance it will cause insert() and update() to fail.

I was in a situation where I needed to mimic some production data in the test environment and it would've been nice to just have an added level of WTF just in case I accidentally triggered a change

@Jaymon
Copy link
Owner Author

Jaymon commented Mar 16, 2016

this could actually be deeper, you could put it on the connection url &readonly=1 and it will cause insert, update, and delete queries to fail at the interface level

@Jaymon
Copy link
Owner Author

Jaymon commented Dec 18, 2017

@Jaymon Jaymon closed this as completed in 091ace7 Jan 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant