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

QtCipherSqlitePlugin #3495

Open
bzctoons opened this Issue Mar 7, 2019 · 3 comments

Comments

Projects
None yet
2 participants
@bzctoons
Copy link

bzctoons commented Mar 7, 2019

Details

Hello I Created a database with : https://github.com/devbean/QtCipherSqlitePlugin
Which is based on wxSqlite but I can't open it with sqlitestudio; Any clue ?
Thanks

@pawelsalawa

This comment has been minimized.

Copy link
Owner

pawelsalawa commented Mar 7, 2019

It's difficult to tell. I assume that password is equal?
Maybe there were some major differences in more recent wxSqlite? (SQLiteStudio uses wxSQLite from a year ago, or even older).

@bzctoons

This comment has been minimized.

Copy link
Author

bzctoons commented Mar 7, 2019

@pawelsalawa

This comment has been minimized.

Copy link
Owner

pawelsalawa commented Mar 7, 2019

What does the status field show when you try to open this database? Is there a message like:
"Could not open database: ...." ?

I'm afraid that the error message (like above) is - by mistake - ignored and not printed to the user when you add new database. It is properly displayed later if DB was already added and there is error re-opening it.

To walkaround this issue I figured out following way:

  1. Create a new wxSQLite database from SQLiteStudio, use the same password as you used for your problematic database.
  2. Open it and close it within SQLiteStudio (to make sure file is created).
  3. Keep SQLiteStudio running.
  4. Replace actual file created with your wxSqlite file
  5. Then try to open in in SQLiteStudio again - it may print the error message at this moment. If not, proceed to next step.
  6. If 5 step worked (no error printed) you either should see your actual database (let me know if you do), or you probably see empty database, as it failed to read schema. If the latter is the case then:
  7. Try to create table in this database. When you try to "commit" new table, it should print actual error.

As for additional logging - yes, you can enable it from command line using -d option. If you use Windows, you will be able to access these logs through debug console (it's in Help menu, or through F12 key). Unfortunately there is not much regrding DB opening issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.