We have a problem with db->api type casting. The error that brought this up was an insertion of a type with a System.DateTime field into a Sqlite table, which does not support datetimes, and so the field is cast to a string. When we pull it back out, we get an error wherein the string is not able to be implicitly cast back to a datetime. A simple attribute which gets handled on CRU operations allowing for the substitution of dotnet types with some specified DB Type will not only fix this error, but also allow the user to extend UDT in flavors like postgres, etc.
We have a problem with db->api type casting. The error that brought this up was an insertion of a type with a System.DateTime field into a Sqlite table, which does not support datetimes, and so the field is cast to a string. When we pull it back out, we get an error wherein the string is not able to be implicitly cast back to a datetime. A simple attribute which gets handled on CRU operations allowing for the substitution of dotnet types with some specified DB Type will not only fix this error, but also allow the user to extend UDT in flavors like postgres, etc.