Still unable to disable prepared statements for both Retool DB staging and production

[Filippo_Galli]

Hi, I saw that this issue should be fixed, but it is still happening on my app

1. My goal: set up staging environment on the app

2. Issue: I cannot disable prepared statements for Retool DB staging, but only production

3. Steps I've taken to troubleshoot: Tried to run the same query with staging and production, in staging is not working

4. Additional info: Cloud, the app is made with the old single page app. It is full of queries so I would rather not move and change all the resources with the hack they proposed in that post.

   I am attaching some screenshots

Unable to disable prepared statements for Retool DB enviroments other than production

There is only one settings page for Retool DB where you can enable the Disable converting queries to prepared statements option. While using other environments than the default production I get errors with queries that need that setting turned on. It is clear that SQL injection protection is turned on here as staging environment uses prepared queries. [Screenshot 2023-09-08 at 17.36.21] [Screenshot 2023-09-08 at 17.36.43] Is there any other way to turn off queries converting to prepared stat…

Thanks,

[Resource_Bot]

Summary

On Retool Cloud, using the classic single-page app builder, the 'Disable converting queries to prepared statements' setting for Retool DB only takes effect in production — it can't be disabled for the staging environment, which breaks queries that require raw/unprepared SQL when setting up staging.

AI Response

This exact behavior was reported and formally resolved: as of version 3.163, toggling 'Disable converting queries to prepared statements' in the RetoolDB resource settings is supposed to apply across all environments, not just production, from the single settings page. Since it's persisting on a current Cloud instance, re-open the RetoolDB resource settings, confirm the toggle state, and re-save it so the setting re-syncs to every environment, then re-run an affected staging query to verify. This points to a regression of the previously fixed issue rather than an intended limitation, so no resource migration or per-query 'hack' should be required.

Sources

Unable to disable prepared statements for Retool DB environments other than production
The original report of this exact bug, closed with a staff-accepted answer confirming the fix shipped in version 3.163 so the setting applies to all environments.

The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a , , or . Or by marking this post as the "Solution"! Let us know if you have any feedback here.

[Filippo_Galli]

Actually what the AI response said worked:
*re-open the RetoolDB resource settings, confirm the toggle state, and re-save it so the setting re-syncs to every environment, then re-run an affected staging query to verify.
*
I guess it just needed to be re-applied.