Skip to content

Conversation

@shioyama
Copy link
Owner

@shioyama shioyama commented Dec 1, 2017

Fixes #94

@shioyama shioyama force-pushed the fix_sequel_5_issues branch 2 times, most recently from 188e18a to 95a41dc Compare December 1, 2017 01:15
@shioyama
Copy link
Owner Author

shioyama commented Dec 1, 2017

So the good news is, Sequel 5 is mostly working fine. The only thing that is failing is query support for the Table backend, because there is code which sets an instance variable on a dataset, and this is no longer possible since datasets in Sequel are now frozen by default and cannot be unfrozen by simply duping them, because dup simply returns (the frozen) dataset.

The problem in Mobility is here, where we set an instance variable to avoid joining the same table more than once. This is admittedly not very nice code, but it serves an important purpose...

@shioyama shioyama force-pushed the fix_sequel_5_issues branch from 95a41dc to ce77fbd Compare December 1, 2017 01:35
@shioyama shioyama changed the title [WIP] Fix Sequel 5 issues Fix Sequel 5 issues Dec 1, 2017
@shioyama shioyama merged commit aab4697 into master Dec 1, 2017
@shioyama
Copy link
Owner Author

shioyama commented Dec 1, 2017

Travis was being stupid about a couple builds, which seemed to be stuck, so I just merged this. It's passing anyway. Full support for Sequel 5.0 - yay!

@shioyama shioyama deleted the fix_sequel_5_issues branch December 1, 2017 06:58
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