You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the query actually returns a large number of rows (in my case), where it should only be one i believe
this is the WHERE clause of the query:
notice that the last OR is alongside the 'post.id =' clause, so its getting the correct post, but also all posts by person.id = 9175 (from joins)
looks like it stems from this rust code:
As a temp fix, i've removed that rust code and it works fine now
The text was updated successfully, but these errors were encountered:
Thanks. I didn't like merging this one, and figured it could cause some problems. It needs a SQL solution, but I don't know the cleanest way to do it. Lets have this a duplicate of #2624 , which I've re-opened.
From Matrix:
the query actually returns a large number of rows (in my case), where it should only be one i believe
this is the WHERE clause of the query:
notice that the last OR is alongside the 'post.id =' clause, so its getting the correct post, but also all posts by person.id = 9175 (from joins)
looks like it stems from this rust code:
As a temp fix, i've removed that rust code and it works fine now
The text was updated successfully, but these errors were encountered: