Re: [Cloud] Toolforge SQL performance issue with new comment table

Sure! I just fetch the comment ID in the original query ([1]), and fetch the comment text with a separate query ([2]). You need *n*+1 queries based on the number of records, but the performance is adequate for my use cases. [1]: main query

Re: [Cloud] Toolforge SQL performance issue with new comment table

Thanks! Performance is much better with that change. On Sun, 2 Jun 2019 at 21:54, Amir Sarabadani wrote: > Hey, > One important optimization you can use and it's often missed out (and it's > going to be needed more as we normalize more tables) is join decomposition. > It basically means you don

[Cloud] Toolforge SQL performance issue with new comment table

t;. I haven't found a way to update those queries efficiently. Is there an optimisation I'm missing? Why does the comment view need subqueries on ten other tables, and is there an alternate version without the subqueries for cases where we just need to join by ID? --

Re: [Cloud] [Cloud-announce] Dropping some comment-related columns in the wiki replicas views (now 3/19/2019)

Is the comment table fully populated, so we can migrate tools immediately? -- Pathoschild (Jesse) On Thu, 7 Mar 2019 at 12:54, Brooke Storm wrote: > After some discussion, we are moving back the date by a week to 3/19/2019 > for people to have a bit more time to update tools and such. > Thanks