The fact that supabase supports graphql has revolutionized it in my mind, thank you! I have confirmed the bug-like behavior, but I have not been able to determine if I am using the system incorrectly or if it is a bug, as similar reports were not reported in the pg_graphql repository. So let me inquire here first. When performing update mutation on an integer column, an error occurs if the value is passed as an argument; "column "xxxxx" is of type integer but expression is of type text" If the value is written directly into the query, no error occurs. Is this a known issue? Also, should I report this in the pg_graphql repository issues?

Hello @aiji42! This thread has been automatically created from your message in #843999948717555735 a ``few seconds ago``. Pinging @User so that they see this as well! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ... menu) and select Leave Thread to unsubscribe from future updates. Want to change the title? Use the

/title

command! We have solved your problem? Click the button below to archive it.