upgrade time dependency version to 0.3

[jdrouet]

The time crate version 0.3.x as been released for a while now and sea-orm is still on version 0.2, blocking the integration with tools like async-graphql which relies on 0.3.x.

PR Info

• Closes upgrade time to 0.3.x version #340

Adds

• create a feature with-time-0_2 to use time@^0.2
• create a feature with-time-0_3 to use time@^0.3

[ikrivosheev]

@jdrouet hello! Thank you for contributation. I think we need support both time = 0.2 and time = 0.3 Because postgres-types has support both time version:

sea-query/Cargo.toml

Line 73 in 79cacdd

postgres-time = ["with-time", "postgres-types/with-time-0_2"]

An example you can see here: #329

[jdrouet]

@krivosheev I'm trying to do as you suggest but run into a problem.
Having both versions in the Cargo.toml, we'd mean aliasing time@0.2 to time-0_2 and time@0.3 to time-0_3.
Which means that for the imports we'd have to do use time_0_2 and use time_0_3.
The problem is that when we use macros like date, time and offset, the procedural macro makes a reference to ::time::... which is not available in our case because it's aliased to time_0_x.
In my case, only the use of format_description is causing a problem for the library and date, time, and offset in the tests.
postgres-types doesn't seem to have this issue because they are not using any procedural macro.
My next iteration will be to remove those macros.

[ikrivosheev]

@jdrouet awesome! Small comment.

[ikrivosheev]

I think deps should be pub(crate), because this is internal mod.

[jdrouet]

well, we need to expose it to use it in tests/*

[ikrivosheev]

Hmm, maybe we need to separating the tests for different time versions

[ikrivosheev]

Or re-import this mod in tests_cfg

[ikrivosheev]

My point was: when we were making some internal mod public it became part of the public API sea-query and every change is breaking...

[jdrouet]

sure, I'll try to fix that. For now I'm trying to find a nice way to fix the CI 😉

[ikrivosheev]

@jdrouet some problems with tests, because tests run with: --all-features

[ikrivosheev]

@jdrouet hello! Thank you for PR. We have done in: #356