[chat quote=“la_219;384;2023-01-30T12:04:41Z” channel=“Elixir Chat” channelId=“2” multiQuote=“true” chained=“true”]
Just a quick question from an Elixir & Ecto beginner: How do I get the result size of a query? I worked with pagination and that worked like a charm but I also need to give the total size to the frontend. Do I need another query for that or is there a more elegant solution?
[/chat]

[chat quote=“kartheek;385;2023-01-30T12:13:26Z” chained=“true”]
You are using any specific pagination library ? Scrivener has those details in the result.
[/chat]

[chat quote=“la_219;386;2023-01-30T12:20:58Z” chained=“true”]
No, so far not. But if it has enough perks, it might be worth it
[/chat]

[chat quote=“kartheek;387;2023-01-30T12:23:36Z” chained=“true”]
https://github.com/drewolson/scrivener_ecto
[/chat]

[chat quote=“la_219;388;2023-01-30T12:28:39Z” chained=“true”]
thank you!
[/chat]

[chat quote=“zachallaun;389;2023-01-30T13:13:05Z” chained=“true”]
@la_219 it might be worth thinking through the problem even if you use scrivener, just as a learning exercise! The critical thing is that everything boils down to a SQL query, which returns rows of records. Barring something like array_agg and building the structs yourself, you’d need/want to include the count on every row of the returned result. In Ecto, that means you’d add a virtual field to your schema definition, something like total_count. You could then join each returned row on every row, selecting a count of those rows.

Another thing to consider is the database you’re using. If you’re over a network, like Postgres, it’s usually better to jam everything into one query. If you’re using SQLite though, since the DB is local, you can sort of ignore the cost of multiple requests and just structure things in whatever way is easiest to reason about!
[/chat]

[chat quote=“la_219;393;2023-01-30T16:33:24Z” chained=“true”]
Thank you! That’s exactly what I ended up doing. I totally agree that it’s worth to solve a problem (at least in theory) first before using a library. I’m working with postgres so getting everything into one query is definitely the preferred way
[/chat]