The driver can only (automatically) retrieve an inserted row if that row contains an auto-increment column.
The table below contains a summary of the types that appear in the table designer when is design view. Please see the MySQL documentation for authoratative details. All MySQL type options may not be available.
Type | MySQL |
TinyInt | 8 bit integer, -128 to 127 signed. |
SmallInt | 16 bit integer, -32768 to 32767 signed. |
MediumInt | Signed range -8388608 to 8388607. |
Integer | "Normal" sized integer, range -2147483648 to 2147483647 signed. |
BigInt | Large integer, -9223372036854775808 to 9223372036854775807 signed. Rekall cannot handle values outside the range of the integer type. |
Float | Floating point value, 24-bit precision, |
Double | Double-precision floating point value. Allowable values are -3.402823466E+38 to -1.175494351E-38, 0, and 1.175494351E-38 to 3.402823466E+38. |
Decimal | Unpacked floating-point value, the number is stored as a character string. |
Date | A date. The supported range is '1000-01-01' to '9999-12-31'. |
Time | Time (hours, minutes and seconds). |
DateTime | Combines date and time. |
TimeStamp | As for DateTime but MySQL automatically sets it to the current time in an insert or update SQL operation if no value is explicitely given. |
Char | Fixed length character string, right-padded with spaces, with length from 1 to 255. Note that bool, which can be used in create table statements, is equivalent to char(1). |
VarChar | Variable length character string; trailing spaces are removed when the value is stored. |
TinyBlob | Binary type, up to 255 bytes long. |
Blob | Binary type, up to 65535 bytes long. |
MediumBlob | Binary type, up to 16777215 bytes long. |
LongBlob | Binary type, up to 4294967295 bytes long. |
The advanced settings for the server dialog are described below.
Ignore MySQL character setThe MySQL server can be configured for a range of character encodings. If this option is not set, and a character encoding has not been set in the common advanced settings, then Rekall will attempt to use the database character encoding. If this option is set, then the MySQL character encoding is ignored.