Cumulusmx.db: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search

Cumulusmx.db (view source)

Revision as of 09:41, 1 October 2022

98 bytes removed ,  1 October 2022
m
→‎SqlCache table
See [[Recent history|'''Recent history''' page]].
 
= SqlCache table =
 
This table is fully managed by CumulusMX. You are not supposed to edit contents, you can view to quench your curiosity.
There is a MX setting ('''Settings''' -->> ''MySQL settings'' -->> '''General Options''' -->> Buffer commands on failure) that when enabled allows failed commands to be stored here. ▼
 
▲There is a MX setting ('''Settings''' --=>> ''MySQL settings'' --=>> '''General Options''' -->=>tick Buffer commands on failure) that when enabled allows failed commands to be stored here. The buffer is lost when CumulusMX is restarted.
 
This table holds a list of MySQL commands that are in the queue for '''[[MySqlConnect]]''' to run again.
* DivisionByZero (certain mathematical operations cannot be handled)
The table has two field:
#key; An autoincrement integer for every SQL statement entered in the cache
#statement; A varchar (string) containing the SQL statement that failed
 
= SQLite Sequence =
Here is the relevant create table instruction, so this tells you the 2 fields in the table as Mark Crossley created it:
No relevant information on this table is known
 
CREATE TABLE "SqlCache"(
"key" integer primary key autoincrement not null,
"statement" varchar)
 
The table contents are simple to explain, each time a new command is stored it is assigned a new number (that is automatically incremented from last number used) and the command itself is stored in a variable text length entry.
 
 
CREATE TABLE sqlite_sequence (`name` TEXT, `seq` TEXT)
Retrieved from "https://www.cumuluswiki.org/a/Special:MobileDiff/10800"

Navigation menu