values_ produces invalid SQL when passed empty list

[thomasjm]

I noticed that a query like values_ [] (against Postgres) produces invalid SQL like this:

SELECT "t0"."res0" as "res0", ... FROM (VALUES ) AS "t0"("res0",...)

The empty VALUES statement causes an error syntax error at or near ")". Maybe it should accept a Data.List.NonEmpty list instead?

[kmicklas]

I'm wondering if there are any workarounds emitting different SQL. The closest I could come up with was:

select * from (select * from (values (null, null)) as dummy(x, y) limit 0) as t(x, y);

but maybe there is something even better.