Leap year when comparing february 2024 and 2023

Bug reports
1

Hello! We are facing a data mismatch when we try to compare revenue from February 2024 and February 2023, because in our SQL we are using "interval '1 year' " in the comparison, but it is currently taking from 1st February 2023 to 1st March 2023 (29 days) when showing the total amount of revenue in February 2023.

Could you please help? Is there any way to set a setting that allows us to set February 2024 as a leap year in Metabase??

We are looking forward to hearing from you

Thank you in advance

2

Metabase does not know anything about leap years, that is the job of your database.

What database are you connecting to?
What SQL is Metabase generating. Unless there is an error in the generated SQL then it isn't Metabase.