-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Database Error - no such table: sessions #18
Comments
I know you stated you've tried with the develop branch, but can you open the file /includes/class/SQL.php and verify this line of code is specifying I've been testing SQLite compatibility recently and I discovered that this persistent mode causes errors whenever the schema is modified by a query. |
I deleted all testing instances afterwards, but now I'm now running 3b136e9, in which I can still reproduce the problem. I forgot to mention that all tests were done using SQLite. |
That's an odd one. Clearly the error is being misreported because if the sessions table didn't exist the problem would occur consistently. My hunch is that this error is the result of some other intermittent connection problem PDO is having. Difficult to diagnose unless I can reproduce it. What version of PHP are you using? |
PHP 5.6.17-3 I will see how it goes using MySQL and let you know. Edit: nothing, couldn't reproduce with MySQL. |
Thanks for testing. I'll dedicate some more time to poking SQLite before the next release. Perhaps I can reproduce the problem. |
I think it has to do with the DB path. I ignored the "full path" message and provided only the name because I saw that the DB was created in the root of my project anyway. Now, if I do pass the full (writable) path, this error is gone. It seems that 2 different locations are being referenced as the DB path. The right one, which exists and feeds most of the page, and the broken one causing the error. From what I read, SQLite creates a missing database file silently, which would explain the |
That's great news. I'm glad to have the mystery solved. ^_^ |
I get the following message in the latest release, the master and develop branches
There's no clear pattern, it can be after browsing a few pages or several, but most of the times after login in as admin and opening
/admin
. Happens on pages that were already visited successfully before too, for logged in and out users. Clearing the cache solves the issue temporarily.Cache, cookies and sessions were cleared before each fresh installation. Referes were enabled.
The text was updated successfully, but these errors were encountered: