Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 653 - added support for DateTimeOffset properties in Redis + Data Types Tests #675

Closed
wants to merge 1 commit into from

Conversation

lajones
Copy link
Contributor

@lajones lajones commented Sep 19, 2014

Added support for DateTimeOffset properties in Redis.
Added tests for all built-in data types for all providers except Azure - which needs special treatment (PartitionKeys etc).
As noted several of the data types are not yet supported on all providers - so these have been moved to a Supplemental set of tests which are implemented only on the providers that support them. As SQL Server and SQLite start supporting these we should move those data types into the BuiltInDataTypes* classes and remove them from the Supplemental ones.

Also added tests for all built-in data types for all providers except
Azure - which needs special treatment (PartitionKeys etc).
As noted several of the data types are not yet supported on all providers
- so these have been moved to a Supplemental set of tests which are
  implemented only on the providers that support them. As SQL Server and
  SQLite start supporting these we should move those data types into the
  BuiltInDataTypes* classes and remove them from the Supplemental
  ones.
@anpete
Copy link
Contributor

anpete commented Sep 22, 2014

:shipit:

@lajones
Copy link
Contributor Author

lajones commented Sep 22, 2014

Checked in with # 8866bf3.

@lajones lajones closed this Sep 22, 2014
@lajones lajones deleted the lajones-140912_DataTypesTests_01 branch September 22, 2014 20:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants