this post was submitted on 25 Jul 2023
54 points (95.0% liked)

Rust Programming

8159 readers
6 users here now

founded 5 years ago
MODERATORS
 

We have an urgent performance problem to get finished. The SQL changes are fine, but it seems the Lemmy test code in Rust is defective. This test is failing after we fixed a faulty stored procedure function in PostgreSQL: https://github.com/LemmyNet/lemmy/blob/13a866aeb0c24f20ed18ab40c0ea5616ef910676/crates/db_schema/src/aggregates/site_aggregates.rs#L157

The underlying Rust code needs to be enhanced to query the SQL table with SELECT site_aggregates WHERE site_id = 1, hard-coded 1 is fine, that is always the local site in Lemmy.

Can you please detail all the code changes so that the read method takes an integer parameter for site_id field?

https://github.com/LemmyNet/lemmy/blob/13a866aeb0c24f20ed18ab40c0ea5616ef910676/crates/db_schema/src/aggregates/site_aggregates.rs#L10C7-L10C7

Right now the query has no WHERE clause, pulling the first row it gets. Thank you.

you are viewing a single comment's thread
view the rest of the comments
[–] RoundSparrow@lemmy.ml 5 points 1 year ago

second reply.

Going over both error messages again, found this: https://stackoverflow.com/questions/70389667/rust-diesel-method-filter-exists-for-schema-table-but-its-trait-bounds-were-n

seems adding:

use diesel::prelude::*;

Might be helping. This compiles now:

    site_aggregates::table.filter(site_aggregates::site_id.eq(1)).first::<Self>(conn).await