-
Notifications
You must be signed in to change notification settings - Fork 105
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
The sqlpage_files
table does not exist
#718
Comments
Hello ! Are you using the same version of sqlpage locally and on the remote server ? Are you sure you did not have a sqlpage_files when you started sqlpage that you then deleted ? The logic in sqlpage is the following:
The error you see seems very strange. If you manage to reproduce it consistently with the latest sqlpage version, I would love to get reproduction instructions. If you have the full verbose logs (including of the time when sqlpage is starting up), that would be useful too! |
It looks like everything is working smoothly on both sides. The remote MSSQL instance has a The local MSSQL instance doesn’t have a The logs don’t show any issues, and queries should be processing normally on both sides. Everything seems to be running just as it should. 😊 |
@lovasoa The I have sent you an email titled |
Hi ! I received your email with the logs, and it indeed seems that there is a problem with sqlpage not detecting the absence of the sqlpage_files table on startup. I'll investigate, and may need you again for testing, since I cannot reproduce this issue locally. |
Hello, I used the
table
component, and the SQL is as follows:When connecting to the local MSSQL, it works fine. However, when connecting to the MSSQL on the server, it reports an error as follows:
Then I manually created the
sqlpage_files
table (on the server's MSSQL), and it worked fine. However, the local MSSQL did not require creating this table. What could be the reason for this?Version information
windows 10 Simplified Chinese zh-CN
MSSQL 2012
0.31.0
Additional context
The console log is as follows:
The text was updated successfully, but these errors were encountered: