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

fallback for sqlite3 #8

Closed
GoogleCodeExporter opened this issue Dec 7, 2015 · 3 comments
Closed

fallback for sqlite3 #8

GoogleCodeExporter opened this issue Dec 7, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Use a more modern system where sqlite3 is used instead of sqlite

What is the expected output? What do you see instead?
The ImportError should be caught and the app should try to import sqlite3 
instead of just crashing.


What version of the product are you using? On what operating system?
3.1
Platform independent.

Please provide any additional information below.
try:
    import sqlite
except ImportError:
    import sqlite3 as sqlite

Original issue reported on code.google.com by bre...@dajool.com on 31 Mar 2011 at 7:55

@GoogleCodeExporter
Copy link
Author

I've written a patch to make yubiserve work sqlite3. (ie, RHEL6)

I would like someone to review my patch (attached).

You will also need to rebuild your sqlite db:

IE:  sqlite3 yubikeys.sqlite < src/dump.sqlite 

Original comment by glen.ogilvie@gmail.com on 4 May 2012 at 3:42

Attachments:

@GoogleCodeExporter
Copy link
Author

Original comment by b1ga...@gmail.com on 4 May 2012 at 9:31

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Code is in place to support sqlite3 as well as sqlite. This has been in SVN for 
some time now.  Marking as fixed.

Original comment by glen.ogilvie@gmail.com on 2 Jan 2013 at 11:08

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant