The condition in the database query does not work

[vv-a2007]

Wappler Version :last stable
Operating System : Mac
Server Model: NodeJS
Database Type: PostgreSQL
Hosting Type: custom

I need that when a zero filter value arrives, the query returns all values ​​and does not take this value into account. And when it was greater than zero, it was selected accordingly. But it doesn't seem to work.

[kfawcett]

What about using a Condition in your workflow and having two different database queries?

As an example, here is how I create APIs. In the GET request, first, I check to see if an id is sent, then I will query for the individual record. Else, I will return all records.

[vv-a2007]

Well, I finally know this method, only I have only 7 types of filters and you can estimate the number of combinations

[kfawcett]

I see. I haven't used the conditions much, so I'm not sure if it can do evaluations. @Teodor shows an example here.

Database Query Ignore Empty Values Conditions

Well Antony, the conditions are there exactly for this purpose. Add a condition for each group and it will be ignored if the condition is not met. So use the $_GET variable as a condition and it will be ignored if the GET variable returns no value ... [Screenshot_20] In my example if {{$_GET.country}} returns a value and {{$_GET.city}} does not - only the country filter will be applied. If {{$_GET.city}} also has a value, then country AND city will be applied.

Also see this.

How to filter a database query?

Ok so it’s not really hard to do this. On your page you need a text input and a select: [Screenshot 2021-05-25 at 10.37.37] I named them name and category but you can add whatever names you need. Your select needs an option without a value <option>Show all</option> [Screenshot 2021-05-25 at 10.38.19] Then in your server action create two GET variables for the filters, these GET vars will get the values from the two inputs on the page: [Screenshot 2021-05-25 at 10.38.42] And in the query…

[Teodor]

What i see in your video should work fine.
Have you actually tested this in the browser, on your page, where a real value is assigned to your GET param? What i see in your video is just testing it in the query builder. These conditions won't actually work in the query builder as the query from the query builder is dynamically being generated on the server and will generate a different query depending on your conditions.

Always test your queries with an actual data, in a real browser.

[vv-a2007]

Yes, thanks, I was able to configure this in a real request