Custom Query - Frontend (bug?)

Hello everyone,

Why my custom queries are not showing as an array inside of a AppFlow in the front end? It’s showing as “string”!

Captura de Tela 2022-12-23 às 20.03.26

Only the first one is correct!

I’m using the last Wappler version.

Is this a bug?

The custom query outputs depend on the schema defined for the query.
What are schemas, what output do they define?

Thanks for you answer @Hyperbytes!
Well… the schema has integer, date and string fields, I use Postgres COALESCE on some fields (to replace null values). All queries returns only one line (using limit 1)

Is there a way to check what is the output of the query?

If you run it directly from wappler using open in browser the output should be visible in the developers console.

It is! Showing as array on browser, but on front end as string… weird

Can think of anything else suggest, maybe needs someone from team to check it out.

I see this regularly with custom queries in wappler. It really shouldn’t matter. You can assign it as an array as required (repeats, tables, etc…) and it will work just fine on front end.

P.S: You may also be able to cast it explicitly as an array on the server using a set value with output on. Turn output on qry off to save network overhead.

1 Like