Cumulusmx.db: Difference between revisions

1,033 bytes removed ,  10:14, 2 November 2022
m
Protected "Cumulusmx.db": Edit warring ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) [cascading]
m (Protected "Cumulusmx.db": Edit warring ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) [cascading])
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
This page is the new ''Cumulusmx.db'' page. This page and subpages hold a complete rewrite of the ''Webtags'' related pages.
The information that was on this old ''Cumulusmx.db'' page has been moved to [[Cumulusmx.db_(preserving_history)|Cumulusmx.db (preserving history)]]. You are advised to use that page until this page is ready and this message has been removed. If any questions or remarks please send a PM to [https://cumulus.hosiene.co.uk/memberlist.php?mode=viewprofile&u=9016 HansR] on the forum. Do not use the ''discussion'' tab unless accompanied by a PM: there is  no automated signal to HansR if you use that page.
This page and its subpages will document the Cumulusmx.db from the point of view of the CumulusMX software and not the Cumulus 1 legacy software. Cumulus 1 is no longer maintained and will eventually disappear. If you are still using it, please refer to the original [[Cumulusmx.db_(preserving_history)|Cumulusmx.db (preserving history)]] page where @sfws has tried to give both packages equal value. That effort is no longer maintained in this ''Webtags'' page. We hope you will understand this approach.
Please do not edit this page while it is being worked on i.e. while this message is still here.
<hr/>
[[Category:Cumulus MX]][[Category:Cumulus Files]]
[[Category:Cumulus MX]][[Category:Cumulus Files]]


Line 181: Line 171:
|}
|}


See [[Recent history|'''Recent history''' page]] for more details.
See [[Recent history|'''Recent history''' page]].
 
= SqlCache table =


=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.
This table holds a list of MySQL commands that are in the queue for '''[[MySqlConnect]]''' to run again.
Line 202: Line 194:
* DivisionByZero (certain mathematical operations cannot be handled)
* DivisionByZero (certain mathematical operations cannot be handled)
   
   
The table has two fields:


Here is the relevant create table instruction, so this tells you the 2 fields in the table as Mark Crossley created it:
{| border="1" class="wikitable"
 
|-
CREATE TABLE "SqlCache"(
! style="width:10px" | Column number #
"key" integer primary key autoincrement not null,
! style="width:80px" | Column name
"statement" varchar)
! style="width:80px" | Column type
 
! style="width:280px" | Properties
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.
! style="width:450px" | Description
 
|-
| 0
| key
| integer
| Primary Key, Not NULL, No Default Value,
| An autoincrement integer for every SQL statement entered in the cache
|-
|-
| 1
| statement
| varchar
| Not NULL, No Default Value,
| Contains the actual SQL statement that failed
|-
|}


CREATE TABLE sqlite_sequence (`name` TEXT, `seq` TEXT)
= SQLite Sequence =
No relevant information on this table is known