About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

SQL Query Case Sensitivity Issue in Zapier - Seeking Assistance

  • 21 November 2023
  • 3 replies
  • 35 views
L

I'm currently encountering an issue with executing an SQL query in Zapier. The SQL query, which works perfectly in pgAdmin, is encountering difficulties within Zapier.

Description of the Issue: When attempting to execute the following SQL query in Zapier:

SELECT * FROM public."User" ORDER BY id ASC LIMIT 100;

(I enclosed the table name in double quotes because the first letter is uppercase.)

I get this error:

The query aims to retrieve records from the "User" table in the "public" schema, ordering them by the "id" column and limiting the results to 100. 

If you have any advice or if you've encountered a similar situation, please share your thoughts.

Thank you for your assistance!

 

 

icon

Best answer by SamB 24 November 2023, 12:54

View original

3 replies

SamB
Rank
Userlevel 7
Badge +11

Hi @lblisa, welcome to the Community! 👋

Hmm, I wonder if it might be having issues because of the “public.” part. I’d normally expect the query to just have the user table referenced as “User” not as public.”User”. I’m thinking it should look like this:

SELECT * FROM "User" ORDER BY id ASC LIMIT 100;


Can you try updating the query to the above and let us know if that fixes it? 

L

Hi @SamB, thanks for your reply! 

I also attempted the following variations without success:

  • FROM "public.User"
  • FROM "User"

The error seems to be that the system does not read the uppercase letter and so claim that the table is undefined.

SamB
Rank
Userlevel 7
Badge +11

Sorry to hear that didn’t solve it @lblisa. Having the table name enclosed in double quotes should be allowing it to be referenced correctly. 

I spotted that you’ve also reached out to our Support team who have opened up a bug report for this issue. As support mentioned, we’re unable to provide an ETA on when it will be resolved by but we’ll be in touch via email as soon as it is.

For anyone who’s running into this same issue and comes across this thread, the recommendation from Support was to rename the table to lowercase in the meantime so that the query can be run successfully. Not an ideal solution I know but hopefully will help to get your PostgreSQL related Zaps up and running for now. 🤞

Reply


Terms & Conditions