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

Making small change so that this can play nice with SQLiteCipher.swift #389

Closed
wants to merge 3 commits into from

Conversation

gblotter
Copy link

Needed to make func check() be public, so that SQLiteCipher.swift can access it in it's extension of the Connection class.

Please let me know what questions you have. if there is a better way of doing this, I'm open to suggestions. If you want to check out the details of the PR I have coming for the SQLiteCipher.swift repository, that uses this change, you can check it out here: https://github.com/gblotter/SQLite.swift/tree/SQLiteCipher-play-nice

@gblotter
Copy link
Author

@stephencelis Any chance you've had a second to check out this PR? 😊

@stephencelis
Copy link
Owner

Not yet, sorry! Will try to find some time later today.

@stephencelis
Copy link
Owner

@gblotter Do you have a link to your use in SQLiteCipher?

@gblotter
Copy link
Author

@stephencelis yeah, there is a a PR waiting for you in the repo w/ my use.

stephencelis/SQLiteCipher.swift#12

@pepejeria
Copy link

Any chance of having this minor PR reviewed? Would be great to have SQLiteCipher sorted out. Thanks

@TheNephilim88
Copy link

+1

@multiholle
Copy link

bump

jberkel added a commit that referenced this pull request Nov 16, 2016
@jberkel
Copy link
Collaborator

jberkel commented Nov 16, 2016

This is now part of #531

@jberkel jberkel closed this Nov 16, 2016
@jberkel jberkel added this to the 0.11.1 milestone Nov 16, 2016
jberkel added a commit that referenced this pull request Dec 5, 2016
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.

6 participants