Question 1

How to save and reload filters with Filtrex in a Phoenix app?

Accepted Answer

Use Filtrex.parse/1 to convert filters into JSON-friendly maps, store them in your database, and later apply them with Filtrex.query/2. The README shows an example with serialization for smart filter features.

Question 2

Filtrex vs writing raw Ecto queries – which is better for performance?

Accepted Answer

Filtrex adds minimal overhead by compiling to standard Ecto queries, but for very simple, static filters, manual Ecto queries might be faster. For dynamic user input, Filtrex saves time on validation and standardization.

Question 3

Can Filtrex handle custom date formats and ranges?

Accepted Answer

Yes, the date type supports comparators like 'between' and allows custom formats via the format option in configuration, as detailed in the filter types section of the README.

Question 4

How to filter across multiple associated tables with Filtrex?

Accepted Answer

Parse separate filters for each model and combine queries using Ecto joins, as demonstrated in the filtering across associations example. This requires manual query composition but is supported.

Question 5

What are the security risks with Filtrex and how to mitigate them?

Accepted Answer

Filtrex validates all parameters against a config DSL to prevent SQL injection and unauthorized access. Ensure your configuration strictly defines allowable fields and types, as highlighted in the philosophy.

Question 6

Is Filtrex compatible with MySQL or SQLite databases?

Accepted Answer

The library is only tested with PostgreSQL per the README, so while it might work with other Ecto adapters, date handling and other features could differ, requiring thorough testing.

filtrex

What is filtrex?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions