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

Support Timestamp property in POCO entities #60

Closed
kzu opened this issue Aug 13, 2021 · 0 comments · Fixed by #61
Closed

Support Timestamp property in POCO entities #60

kzu opened this issue Aug 13, 2021 · 0 comments · Fixed by #61
Labels
enhancement New feature or request

Comments

@kzu
Copy link
Member

kzu commented Aug 13, 2021

It's sometimes useful to be able to read the Timestamp value managed by Table Storage, so we should just allow POCOs to be able to read it by just declaring a property with that name.

Back this issue
Back this issue

@kzu kzu added the enhancement New feature or request label Aug 13, 2021
kzu added a commit that referenced this issue Aug 13, 2021
It's sometimes useful to be able to read the Timestamp value managed by Table Storage, so we just allow POCOs to be able to read it by just declaring a property with that name.

Fixes #60
kzu added a commit that referenced this issue Aug 13, 2021
It's sometimes useful to be able to read the Timestamp value managed by Table Storage, so we just allow POCOs to be able to read it by just declaring a property with that name.

Fixes #60
@kzu kzu closed this as completed in #61 Aug 13, 2021
kzu added a commit that referenced this issue Aug 13, 2021
It's sometimes useful to be able to read the Timestamp value managed by Table Storage, so we just allow POCOs to be able to read it by just declaring a property with that name.

Fixes #60
@devlooped devlooped locked and limited conversation to collaborators Oct 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant