V0.33.2 graph strange behaviour

Hello,

Thank you guys for your reactivity and your speed for the 0.33.2 update, it solved a lot of our issues.
I have noticed a strange behavior concerning time-series.
Somehow, now Metabase expects to have the time column as a first row for timeseries. :
For example this query works, you can have a nice graph:

WITH time_window AS (
SELECT date_trunc(‘day’, dd)::date as dayy, 1 as user_id
FROM generate_series ( ‘2019-01-01’ , ‘2019-01-10’, ‘1 day’::interval) dd
)
select
dayy,
1 as column_1,
2 as column_2
from time_window

But this query doesn’t:

WITH time_window AS (
SELECT date_trunc(‘day’, dd)::date as dayy, 1 as user_id
FROM generate_series ( ‘2019-01-01’ , ‘2019-01-10’, ‘1 day’::interval) dd
)
select
1 as column_1,
dayy,
2 as column_2
from time_window

Is it normal ?

Thanks a lot!

1 Like

Hi @Ombenz
That definitely looks like a bug. When I do a similar query on 0.32.10, then it works (just have to adjust which fields are on X/Y-axis), but on 0.33.2 it breaks.
EDIT: For reference: