Ah! I was worried that might be the case. It looks like we have a bug report for exactly this (we don't currently support null values with BigQuery queries). I just bumped it to the PM, so hopefully we'll have good news for you soonβI'll keep you updated in this thread!
This is currently blocked on the Retool side, but we've bumped it to the team in hopes of a resolution soon I'm sorry about the delay here and will keep this thread updated!
Also how should I pass my query column name in place of null
Example
MERGE bqtable1 AS a
USING UNNEST({{table16.recordUpdates }}) AS b
ON a.uuid = b.uuid
WHEN MATCHED THEN
UPDATE
SET
a.address = {{ {RT$BQTYPE: 'STRING', value: b.address} }}
Anyway, I tried to implement above logic in all possible ways. But that's not working for me. Maybe it on small scale like above, but in most common cases like when we try to update the table or insert new values this doesn't works.
And this issue is really kind of annoying as we have to fill our tables with empty strings ("") instead of null. That creates confusion while working on BigQuery console, whether to use is null or to use length(column) = 0, Also it requires to put additional logic on retool. From last 7 months we're dealing with this issue.
Is it too difficult to resolve this?
I think instead of making retool's GUI more intuitive please figure out this null issue as it's becoming very painful. and that's actually the base of whole retool app.