By default, Chartio sets data sources to read-only at the connection level. This provides an additional layer of security against malicious queries.
Some databases, such as Redshift, disallow the creation of variables and temporary tables when connections are set to read-only. For this reason, we allow Redshift users to disable the enforcement of read-only in their data source settings if needed.
If you are seeing an error message like “Error: Transaction is read-only”, disabling the read-only setting should resolve this issue.
Even with read-only disabled, your database is still protected from malicious queries in two ways:
- a user-provided read-only login Chartio uses to connect to your database
- Chartio’s disallowed keywords list that blocks queries with malicious keywords