Timeline for Arbitrary queries on n:m relationship, including "all" and "any"
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2020 at 22:25 | history | edited | CommunityBot |
added [postgresql-performance] to 571 questions - Shog9 (Id=1924)
|
|
| Jan 2, 2018 at 8:58 | vote | accept | Alex Hornung | ||
| Jan 2, 2018 at 1:54 | history | edited | Erwin Brandstetter | CC BY-SA 3.0 |
tags
|
| Jan 2, 2018 at 1:49 | answer | added | Erwin Brandstetter | timeline score: 2 | |
| Dec 31, 2017 at 15:12 | history | edited | McNets | CC BY-SA 3.0 |
added 153 characters in body; edited tags; edited title
|
| Dec 31, 2017 at 10:27 | comment | added | Alex Hornung | In general, I'd still also like to know a bit more about the efficiency of the query I wrote, and whether any index could help. | |
| Dec 31, 2017 at 10:27 | comment | added | Alex Hornung | Still working through that linked answer, but it's hard to see how that can be built relatively easily programmatically for an "arbitrary" user-provided high-level query. Most of it is quite specific to two "things", and if you want only 1 or more than one, or an OR instead of an AND, the query changes significantly. That's the main reason I came up with the query I came up with - it allows to just generate a bunch of where clauses in a single place, and join them together with OR/AND for the desired effect. | |
| Dec 31, 2017 at 9:57 | comment | added | ypercubeᵀᴹ | The answer in the linked question has done some efficiency tests of the various (more than 10) methods of performing similar queries. | |
| Dec 31, 2017 at 9:52 | comment | added | Alex Hornung | I've clarified the question a bit to also ask about the efficiency of the query I came up with, and whether any sort of index could help it. Ideally, I'd like a query that is easy to build programmatically, and also reasonably efficient. However, I do have the option of limiting the amount of querying I do via SQL, and simply do the rest in the backend/service itself - so I certainly would like to understand the efficiency of the SQL part of the query. | |
| Dec 31, 2017 at 9:51 | history | edited | Alex Hornung | CC BY-SA 3.0 |
clarification around performance questions
|
| Dec 31, 2017 at 9:49 | comment | added | ypercubeᵀᴹ | Take a look at this question and the accepted answer: How to filter SQL results in a has-many-through relation | |
| Dec 31, 2017 at 9:47 | comment | added | ypercubeᵀᴹ | Is your aim a generic query or an efficient one? | |
| Dec 31, 2017 at 9:36 | review | First posts | |||
| Dec 31, 2017 at 10:31 | |||||
| Dec 31, 2017 at 9:34 | history | asked | Alex Hornung | CC BY-SA 3.0 |