| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- Indentation fixed
- Logic of empty string fixed
- Added read_variable_length() to opaque data type
- Added logic and test case for MYSQL_TYPE_NEWDECIMAL
- Added new utf8 test
- Added support encoding for other opaque data types
(MYSQL_TYPE_{LONG/MEDIUM/TINY}BLOB, MYSQL_TYPE_VARCHAR, MYSQL_TYPE_YEAR) found in json
suite of mysql and test cases
- Added big array test (--do-test=anel/mysql_j)
- alter force @todo
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
- Have to change length to support 2 bytes only (large=false)
- Have to use `read_variable_length()` since length of 8th bit of each
of 5 maximum allowed byte needs to be validated - this should be done on
OPAQUE type also @todo
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- sql-common/my_time.c -> my_TIME_to_str() has already implemented
format just add that case using appropriate `time_type`
- finished this types
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- Support datetime -> parsing needed for date/time @todo(maybe)
- Except this patch, mysql is handling specially `MYSQL_TYPE_NEWDECIMAL` and the rest is default @todo(maybe)
- my_base64 (wrapper_to_string() ) ->@todo(maybe)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- Added a test case for ints ->works
- Same analogy should be applied to other int types ->todo with tests
- Analysis done
|
| |
|
|
|
|
| |
- Test is working for string and int16 data type
- Test is not working for INT32 and UINT64 data type
- Analysis done
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Used `string::append_longlong()` and is looking as:
```
(gdb) p buffer->Ptr
$1 = 0x7fffe00306e8 "{\"a\":2}"
```
@todo test with big >0 and <0 ints in mysql
- After this step strings are getting double qoutes (mysql has
`double_qoute()`
```
(gdb) p buffer->Ptr
$1 = 0x7fffe004ae48 "{\"key1\":\"val1\",\"key2\":\"val2\"}",
```
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- Added parsing of mysql binary wrt KEY_ENTRY_SIZE and VALUE_ENTRY_SIZE
of json object only (@todo- json array)
- Added parsing of string value (@todo- add new function)
- (todo- add all other types supported by mysql)
- @todos- after review
- Output:
```
(gdb) p buffer->Ptr
$1 = 0x7fffe004ae48 "key1:val1,key2:val2"
```
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- Enable to compile on fresh installation of `10.3`
- Don't use `auto_ptr`, use `unique_ptr` instead
- Enable to compile for all storage engines
|
| |
|
|
|
|
| |
- Server can read .frm files and get the output from json native mysql
type
- Test case is coverd in this milestone
|
| |
|
|
|
| |
Part#2: Remove other unneeded files which cause compile
warnings-treated-as-errors errors on Windows.
|
| |
|
|
|
|
| |
Don't compile table/mock_table.cc
(pushing this patch to 10.3 first to make sure it fixes the issue
will push to 10.2, too)
|
| |\ |
|
| | | |
|
| | | |
|
| |\ \
| |/ |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
- Changed the assert to ignore SRV_LOG_SPACE_FIRST_ID. Post push
fix to address the previous commit failure.
|
| | |
| |
| |
| |
| | |
Changed the debug insert inside fil_io() to check whether it writes
the page to wrong offset only for user tablespace.
|
| | |
| |
| |
| |
| | |
- log_crypt_init() should be called from create_log_files(). Because
it should re-create the new random nonce compared to the old ones.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The test innodb.leaf_page_corrupted_during_recovery
fails on buildbot with
Warning 1406 Data too long for column 'line' at row 10
line
len 16384; hex ...
because of a page dumps that InnoDB is generating for a corrupted page
Since this test is using debug instrumentation, we will solve the
issue by disabling page dumps in debug builds altogether. Users of
debug builds will likely know how to extract page dumps in other means.
Page dump output could sometimes be useful when diagnosing problems
that users are facing. Hence we will keep the page dump output in
non-debug (release) builds.
|
| | |
| |
| |
| |
| |
| |
| | |
if innodb_encryption_threads > 0
- Avoiding accessing encryption thread mutex before initiating
the encryption threads
|
| | |
| |
| |
| |
| |
| | |
- Ported mysql Bug#20597981 test case to mariadb-10.2
- InnoDB never used fts_doc_id_in_read_set. Basically it tells
innodb to read the fts_doc_id from the index record itself.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Introduce a new variable called innodb_encrypt_temporary_tables which is
a boolean variable. It decides whether to encrypt the temporary tablespace.
- Encrypts the temporary tablespace based on full checksum format.
- Introduced a new counter to track encrypted and decrypted temporary
tablespace pages.
- Warnings issued if temporary table creation has conflict value with
innodb_encrypt_temporary_tables
- Added a new test case which reads and writes the pages from/to temporary
tablespace.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Added the condition in innochecksum tool to check page id mismatch.
This could catch the write corruption caused by InnoDB.
Added the debug insert inside fil_io() to check whether it writes
the page to wrong offset.
|
| | | |
|
| | | |
|
| | | |
|
