- My goal: eliminate hard coding of schema name for postgres in query GUI mode
- Issue: my developers have been using the gui mode of CRUD queries to simplify, structure and manage CRUD queries. Unfortunately, for postgres it seems to hard code the schema name. Which defeats the environments approach. I have three environments (dev, stage, prod), to follow pretty common and basic development practices. the environments setting works well with connections and i've found ways to restrict developers to certain environments. HOWEVER, while the GUI mode on the queries is really nice for structure and cleaner development, when you switch an app from one environment to another the hard coded schema causes the query to fail. Which means you must go into every single query and change the source table. For a single form that could be 3-5 or more queries. for an app, could be dozens. which means you can't quickly migrate from one environment to another or test across environments. This is a HUGE problem. is there a workaround for this?
- Steps I've taken to troubleshoot: Tried eliminating the schema name in the table name in the gui but the retool validations simply wipe it out. I've also looked to see if i could build it dynamically based on the query. No dice.
- Additional info: (Cloud or Self-hosted, Screenshots). Business cloud hosted. Another disappointment of retool. SO close. Absent any workaround, i'm going to have to have developers go back and refactor a couple weeks worth of work. Very disappointing for a "low code" tool.
