Expired verifications causes primary key conflict when attempting to verify about toucan HOT 3 CLOSED

hi @bjammin, thanks for all the recent feedback!

no need for above code change - the underlying cause is incorrect instructions in the ef scaffolding

it was accidentally setting the 'user id' field as the primary key, rather than the 'code field' (which is a guid string).

easily fixed!

from toucan.

this one has actually highlighted a bigger issue which I need to think about for a bit =S

how you supply dates when writing ef queries varies depending on the target provider (postgres or mssql). pgsql ef provider expects a local datetime as input. mssql ef provider expects a utc datetime as input.

once you scaffold out a solution, you tie it to one particular ef provider, and it's not a problem going forwards. all the code you write will be consistent in it's use of local or utc when writing queries.

but 'system' code has to be agnostic about what ef provider it is querying. i will have to do some research, and think about what is appropriate. probably just an extension method :)

if you have any thoughts, let me know!

from toucan.

coded a fix. will include in deployment for next release.

from toucan.