-
Notifications
You must be signed in to change notification settings - Fork 21
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
Tweak how options[:temporal] is handled #97
base: master
Are you sure you want to change the base?
Tweak how options[:temporal] is handled #97
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks sensible, thank you.
Looks like this project has begun to be maintained again, so I've merged upstream master. If this PR is still useful would it be possible to get it in the next release? |
Hi, same considerations as the other PR. Any chance to rebase instead of merge and provide a failing test case? |
…tate in the case of a user manually managing "search_path"
4ab3d25
to
6a2aa61
Compare
@tagliala I've finally come back to this, including adding specs and reworking some functionality. I hope it's good to go now, please let me know if you'd like any further changes |
Hi @pnomolos, Just a heads-up to say thanks because I've cherry-picked some of these commits and merged them into master to fix an issue with |
I still need to write specs for this, but it changes how
options[:temporal]
is handled so that if you don't pass anything explicit it'll work fine (rather than right now, where if you don't specifytemporal: true
on a chronomodel-handled table it'll return it to a plain table).