support for Duration

[matt-beanland]

ash-project/ash#2036 is adding Ash.Type.Duration (short name :duration), ash_postgres should store Duration structure as Postgres interval, and should handle expressions with operators involving durations in the datalayer.

[matt-beanland]

The related issue support for duration on ash_csv failed without an implementation of String.Chars Protocol on Duration.

For postgres we want to use interval in the datalayer, which would require work in ash_postgres.

[matt-beanland]

I've forked and updated deps (ash 3.5.12 etc) however there are failing tests (with postgres 17). It is also very slow, so something isn't right. Might wait for the next release of ash_postgres...

Failing tests include:

• test tuple type with force_attribute_change can be updated (AshPostgres.Test.TupleTest)
• test calculations that refer to aggregates can be authorized (AshPostgres.CalculationTest)
• test sum aggregates show the same value with filters on the sum vs filters on relationships (AshSql.AggregateTest)

[zachdaniel]

Just needs to be using latest versions of ash_sql and ash for those tests to pass I believe.

[zachdaniel]

The tests are very slow, try skipping migration generator tests with mix test --exclude migration

[zachdaniel]

I guess you said you updated deps though, so maybe something is wrong.

[zachdaniel]

Okay, tests should be fixed 😄

[matt-beanland]

Thanks, so we'll need an AshPostgres.Interval using Ash.Type implementing the dump_to_native behaviour.

[zachdaniel]

Would that mean the end user can't use the built in duration type? Ideally we'd wrap that in ash_postgres automatically so they can just use durations and we just handle that when type casting automatically.

[matt-beanland]

Yes I think we can make it work. BTW I still have the same failed tests with ash 3.5.12 and ash_sql 0.2.76, is there something I need from main that hasn't been released yet?