albertored
ex_sieve is a library offering a filtering solution for Ecto. It builds Ecto.Query structs from a ransack inspired query language.
It was originally developed by @valyukov, a few months ago I joined the project and started extending his great work. I have just released version 0.8.0, it includes a lot of new features and improvements, you can take a look at the changelog and at the documentation.
Any feedback is welcome!
Trending in Announcing
Flop is an Elixir library that applies filtering, ordering and pagination parameters to your Ecto queries.
offset-based pagination with...
New
I needed to reuse React components from my Chrome extension in my Phoenix/LiveView backend. I noticed that for Svelte/Vue, there are live...
New
I released Doggo, a collection of unstyled Phoenix components.
https://github.com/woylie/doggo
Features
Unstyled Phoenix components....
New
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hello
Published a new library - ProcessHub!
ProcessHub is a library designed to manage process distribution within the Elixir cluster. ...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
This showed up on my feed.. anyone heard of it? Just hype?
Ox Alpha is a reasoning model designed for coding, sustained ag...
New
Hey folks,
I just published a post about Hologram’s funding and where the project goes next - the short version:
Curiosum as Main Spons...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex










Showing Posts 1 to 9- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
brightball
I’m not familiar with ransack. Can you describe a good use case?
albertored
The documentation contains some example.
The main use case is to create a filter query on a list view taking as input user supplied URL query parameters. But this is not the only possible use, the
Repo.filterfunction provided by the library takes as input a map that can be built in many different ways.LostKobrakai
I’m wondering why you didn’t implement
Ecto.Queryablefor a struct holding the filter input.then this would be usable with all Repo functions and not just your custom injectedMisunderstoodfilter/2.Repo.filter, which does return a query.albertored
Yes, maybe the API it’s not the better one but I didn’t consider changing the original one before releasing 1.0.0. Your suggestion it’s indeed good, I will investigate on it, thanks!
Also for release 1.0 I would like to remove the remaining usage of
Ectointernal APIs. In particular I didn’t find a way of building dynamic joins without relying onEcto.Query.Builder.Join.join/10.Eiji
I did not look into your code, but generally you can simply write a macro for it
albertored
I admit I am not the bigger expert on macros but I tried with no success. The main problem is that all parameters needed for building the join are known only at runtime.
Any suggestion is welcome!
Eiji
Not sure if this code is best, but at least it does not depend on private
API:Notes:
evalhere I have added some guards. To make sure nothing would explode you may add extra runtime checks (regex?) forparentandrelationcontents.import Ecto.Queryand remove unusedalias Ecto.Query.Builder.Joinandjoin_binding/1private function.albertored
Nice! Thanks, I haven’t thought about using
Code.eval_quoted…dalerka
Ex_sieveseems very powerful, yet there’s also a simpler library - Flop - also in early dev stage. Kudos to authors and contributors!Can someone well-versed in Ecto comment about the benefits and downsides in regard to how both libraries approach DB querying, eg. security, performance, query-composing and general dev experience?