Mapping a TimeSpan in a collection component mapping maps as a BIGINT
Description
Environment
None
Attachments
1
Activity
Show:
Frédéric Delaporte July 10, 2017 at 4:43 PM
was about changing the name, but the trouble was applying to the type too.
Philip Ratcliffe June 28, 2017 at 12:05 PM
I've re-uploaded without the dlls in the packages folder.
Frédéric Delaporte June 27, 2017 at 6:12 PM
Re-uploaded without any binaries. Nuget packages were still in the previous one.
Philip Ratcliffe June 27, 2017 at 5:49 PM
Hi,
I couldn't edit the ticket to remove the old cs files, but I have uploaded an updated test, without binaries, as a zip.
Kind regards
Phil
Frédéric Delaporte June 26, 2017 at 5:37 PM
Upload zip without binaries. They are supposed to be restored by nuget or by compilation.
Who's Looking?
If you map a collection of value objects using a component mapping, and the value object has a TimeSpan property, the TimeSpan property maps as a BIGING rather than as a time, even if you have explicity mapped the property as a TimeSpan in your mapping.
Note the bug only applies to the implementation of IComponentElementMapper. The implementation of IMinimalPlainPropertyContainerMapper maps the property as a time, as expected.
(P.S. My zipped test file exceeded the max upload size, so I've just uploaded the cs files needed for my entity, mapping, and test)