Author Topic: ☞ How to stop Sqlite errors  (Read 965 times)

Stopping Sqlite Errors

A lot of users have been complaining about Sqlite errors appearing around and crashing Blockland users recently. I decided to make a thread telling on how to stop those pesky errors and stop people from spamming the forum board.

Sqlite errors happen when Blockland cannot write to the disk database. This happens when you're running Blockland from a CD-ROM or a external disk.

Method 1 - Run Blockland from your computer, don't run it from .zip files or CD-ROMs.
Make sure the user has permission to write data in the folder.

A normal computer under default configuration will let programs write to disk.  There are an infinite number of ways you could have broken this functionality.  It is your responsibility to unbreak it. (most in Windows)

If you want to "unbreak" it, you must ask your Administrator to change the permission settings to your account. 

Method 2 - Delete cache.db in your Blockland directory.
This is the most efficient method.

Thanks for reading this, please provide constructive feedback on this post, and if there's wrong information located on this post, please correct me.

This is all OLD stuff.
What you said I already know and didn't tell me anything. I have read and write permission from the admin, and it isn't broken.
Splite errors are possibly not reversable on a Mac, because i have read and write privileges.

What you said I already know and didn't tell me anything.
Well, then you don't need any help.
This is for the people who need help.

I do need help.
I get Splite errors and crash because of this.

I do need help.
I get Splite errors and crash because of this.
Delete your cache.db every once in a while.

I do need help.
I get Splite errors and crash because of this.
I have a theory, and it's probably invalid, but it can't hurt anything.

warning: I've never used a Mac except for 5 minutes at a Best Buy.

  • Open up finder and browse to wherever Blockland is installed. Get the absolute path. I don't know how to do this in Finder. You can tell an absolute path (from the root) from a relative path (from your current directory) on POSIX systems based on whether or not they start with a "/". For example, /home/austin/random-crap/nope.avi would be absolute, while random-crap/nope.avi would be relative. Mac, *BSD, and Linux use POSIX paths.
  • Open up a terminal. I think you can get one if you click the "Applications" folder on the dock, then "Utilities", and the Terminal icon. I can't remember exactly.
  • Type "cd (ABSOLUTE PATH FROM STEP ONE)" and hit enter.
  • Type "chmod 777 cache.db" and hit enter.
  • Type "exit" and hit enter. We're done with the terminal.

I doubt that will help, but it might. That shouldn't hurt anything except that you're giving world read-write permissions to your cache.db file, but I doubt that could be used for malicious intent.

Semi-OffTopic:
SQLite is supposed to be rock-solid. I don't really get why it's causing issues.

I run Blockland in Wine over Linux Mint and I have to restart BL to update my Internet server list (the loading bar just freezes) or to quit a server and join another (it will show the legendary cache database popup while the server is loading). I'm happy it even works at all though, because BL is for Mac and Windows, not Linux. I love wine.