103 reputation
3
bio website kristengilden.eu
location Tallinn, Estonia
age 23
visits member for 2 years, 4 months
seen Sep 28 at 16:21

Jul
1
comment Why do aggregate functions alter the way my rows are fetched?
Nice answer, thanks! I went with the first approach and it's performing much better. For some reason I thought for each row regular indexes would store a pointer to its relating row. Am I right to assume that in the 1st query MySQL didn't use the whole index as a scan in the table must have been made anyway?
Jul
1
awarded  Scholar
Jul
1
accepted Why do aggregate functions alter the way my rows are fetched?
Jun
30
awarded  Supporter
Jun
30
revised Why do aggregate functions alter the way my rows are fetched?
Yet another typo fix
Jun
30
comment Why do aggregate functions alter the way my rows are fetched?
@ypercube I'm selecting a specific stock from the stock table, join its points and group them by yearweek. I'm sorry if I'm missing something obvious here, but which part of the query do you think is broken? Yes, ´p0.id´ and ´p0.datetime´ make no sense in the context of the query, they are there to keep the application from blowing up.
Jun
30
comment Why do aggregate functions alter the way my rows are fetched?
@Phil Ah, this indeed is the case. Are there any ways to make the initial query perform any better?
Jun
30
comment Why do aggregate functions alter the way my rows are fetched?
@ypercube Slight brain fart there. I fixed the second query so that the only difference between the two is using and not using aggregate functions. The missing (s0.symbol = 'AMD') was a typo and the difference in performance is still there.
Jun
30
revised Why do aggregate functions alter the way my rows are fetched?
Fixed typos
Jun
30
awarded  Editor
Jun
30
comment Why do aggregate functions alter the way my rows are fetched?
Small typo, I fixed it. Thanks.
Jun
30
revised Why do aggregate functions alter the way my rows are fetched?
Typo fix
Jun
29
asked Why do aggregate functions alter the way my rows are fetched?