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

SQLite database file state inconsistent via Mountain Duck #10427

Closed
cyberduck opened this issue Aug 9, 2018 · 1 comment
Closed

SQLite database file state inconsistent via Mountain Duck #10427

cyberduck opened this issue Aug 9, 2018 · 1 comment
Labels
bug sftp SFTP Protocol Implementation thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

8a60be1 created the issue

I have a web server running Ubuntu 16.10, where I have stored an SQLite database

On my own computer, a Windows 7 machine, I have Mountain Duck attached to the web server via SFTP. From my machine, this is accessible via M:\opt\db\cms_config.sqlite.

I have been performing work and updates on the database using SQLiteStudio. However, when I run a query on that database directly from the Ubuntu webserver, I get different results than when I run the same query from my own computer. I downloaded a copy of cms_config.sqlite using WinSCP and compared it to the copy I can see on M:\opt\db\cms_config.sqlite. They should be identical. However, they are not. They are essentially two completely separate copies, and have apparently remained separate since I first copied cms_config.sqlite to the ubuntu server a few days ago.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please write to [mailto:support@mountainduck.io]. This bug tracker is reserved for issues in Cyberduck.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug sftp SFTP Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

1 participant