-
Notifications
You must be signed in to change notification settings - Fork 1
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 block #75
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
What's the point for sqlite? IMO sqlite will be soo heavy with CC and lua. Plus, concurrency on sqlite is terrible |
SQLite Databases could be useful to store persistent data for a program such as a chatbox service, especially considering the very limited space that CC computers have where this block wouldn't have that issue since it's a single dedicated DB |
We must give a deep thought on SQLite:
|
2 could be solved similarly to how CC computers are, where they only get assigned an ID once accessed (and therefore only get assigned a database once accessed) |
No, turtle can easily to automate that process you know |
There's a solution to players intentionally wasting space like that, it's called a ban hammer or /ban |
The cryptographic is dup with #55 |
This sounds fairly similar to the SirEdvin's Cloud Solutions mod. Also not certain how this has an advantage over a lua key-value store. |
Describe your idea
The Cryptographic Accelerator would provide CC computers with common cryptographic algorithms done on the Java side which is faster than implementing them in Lua, possible algorithms could be AES, RSA, and others, as well as a secure RNG, and some common hashing algorithms.(duplicated)The SQLite block would provide access to an SQLite database on the peripheral, stored by ID similar to a computer. The databases would be stored in /world/computercraft/sqlite_block/[id].db
Describe alternatives you've considered if you've any
No response
Additional context
No response
Linked Issues
No response
The text was updated successfully, but these errors were encountered: