Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Console View


Categories: connectors experimental galera main
Legend:   Passed Failed Warnings Failed Again Running Exception Offline No data

connectors experimental galera main
f235f1ce4576...
f235f1ce4576ef9dc498c71cad9094de43b9540f
Alexander Barkov
Switching libmariadb to "Libmariadb changes for MDEV-27009 Add UCA-14.0.0 collations"
f00ac20b0304...
f00ac20b0304f169c9436f36d7aaf3e88910738a
Marko Mäkelä
Merge 10.6 into 10.7
e9adc3959ef2...
e9adc3959ef2e905159dad07b601e41bc0e2dd87
Alexander Barkov
A cleanup for MDEV-27896 Wrong result upon `COLLATE latin1_bin CHARACTER SET latin1` on the table or the database level

Changing the error messages in a statement like this:

CREATE DATABASE db1
        COLLATE utf8mb4_bin
        CHARACTER SET utf8mb4
        CHARACTER SET latin1;

from
  COLLATION 'utf8mb4_bin' is not valid for CHARACTER SET 'latin1'

to a more expected:

  Conflicting declarations: 'CHARACTER SET utf8mb4' and 'CHARACTER SET latin1'

In order to do this:
- Adding a new type TYPE_CHARACTER_SET_COLLATE_EXACT into
  Lex_exact_charset_extended_collation_attrs_st

- Removing m_had_charset_exact from its descendant class
  Lex_extended_charset_extended_collation_attrs_st

Additional cleanup:
- Changing methods in Lex_exact_charset_extended_collation_attrs_st
  set_charset(), set_charset_collate_default(), set_charset_collate_binary()
  to get Lex_exact_charset instead CHARSET_INFO as a parameter,
  to guarantee that the argument is only CHARACTER SET and does not have
  any COLLATE clauses yet. This change is not directly related to
  the error message change.
c2bae9c77f26...
c2bae9c77f2684e3e23a4de7ab5835320bd0be79
Marko Mäkelä
Merge 10.7 into 10.8
babb803222d4...
babb803222d4a5d5a3256720c59d056cc8ba7dc3
Vladislav Vaintroub
MDEV-28648 main.ssl_timeout fails with OpenSSL 3.0.3

Depending on OpenSSL version, and at least in 3.0.3, the client-side socket
timeout is reported as generic error (SSL_ERROR_SYSCALL), losing further
details (both errno and GetLastError() return 0). This results in client
reporting "Unknown OpenSSL error" 2026, instead of another generic
"Lost connection to server during query" 2013

Adjusted test case.
a34373a6c3c6...
a34373a6c3c6bad955792eda5c58bd2d81a7f0d7
Alexander Barkov
MDEV-27009 Add UCA-14.0.0 collations - adding version aware implicit weight handling

Implicit weights are now handled according to the Unicode version
(14.0.0 vs earlier versions).

- Adding a new member MY_UCA_INFO::version

- Copy logical positions and the version from "src_uca" to "new_uca"
  in init_weight_level().

- Adding a "const MY_UCA_INFO *" parameter to a few functions
  to know Unicode version to generate implicit weights accordingly:
  - during the collation initialization time, to pages which are
    a mixture of explicit and implicit weights
  - during comparison time, for fully implicit pages
a2bdd5283584...
a2bdd528358418608e5bacf17a0d70da83b763d5
Daniel Black
Merge branch 10.5 into 10.6
99566fc89429...
99566fc89429481797f4aea3f011545c7b3bb417
Norio Akagi
MDEV-27892 Improve an error message for foreign server exists

Improve and add more languages for the ERROR 1476: Foreign Server
already exists.
8729dd6c7ef0...
8729dd6c7ef036abf438dffc3f5029948274e591
Alexander Barkov
MDEV-27266 Improve UCA collation performance for utf8mb3 and utf8mb4

Adding two levels of optimization:

1. For every bytes pair [00..FF][00..FF] which:
  a. consists of two ASCII characters or makes a well-formed two-byte character
  b. whose total weight string fits into 4 weights
    (concatenated weight string in case of two ASCII characters,
    or a single weight string in case of a two-byte character)
  c. whose weight is context independent (i.e. does not depend on contractions
    or previous context pairs)
  store weights in a separate array of MY_UCA_2BYTES_ITEM,
  so during scanner_next() we can scan two bytes at a time.
  Byte pairs that do not match the conditions a-c are marked in this array
  as not applicable for optimization and scanned as before.

2. For every byte pair which is applicable for optimization in #1,
  and which produces only one or two weights, store
  weights in one more array of MY_UCA_WEIGHT2. So in the beginning
  of strnncoll*() we can skip equal prefixes using an even more efficient
  loop. This loop consumes two bytes at a time. The loop scans while the
  two bytes on both sides produce weight strings of equal length
  (i.e. one weight on both sides, or two weight on both sides).
  This allows to compare efficiently:
  - Context independent sequences consisting of two ASCII characters
  - Context independent 2-byte characters
  - Contractions consisting of two ASCII characters, e.g. Czech "ch".
  - Some tricky cases: "ss" vs "SHARP S"
    ("ss" produces two weights, 0xC39F also produces two weights)
7fe474fe7e25...
7fe474fe7e25cb503b585755c7e0a036e01e0df7
Thirunarayanan Balathandayuthapani
MDEV-25257  SEGV in fts_get_next_doc_id upon some INSERT

- InnoDB fails to create a fts cache while loading the innodb fts
table which is stored in system tablespace. InnoDB should create
the fts cache while loading FTS_DOC_ID column from system column.
78412ab02850...
78412ab028509f07a801c9bf1f3792ad77bcfac6
Honza Horak
MDEV-27778 md5 in FIPS crashes with OpenSSL 3.0.0

OpenSSL 3.0.0+ does not support EVP_MD_CTX_FLAG_NON_FIPS_ALLOW any longer.
In OpenSSL 1.1.1 the non FIPS allowed flag is context specific, while
in 3.0.0+ it is a different EVP_MD provider.

Fixes #2010

part of MDEV-28133
77e1de208adf...
77e1de208adf7f5f3e92aa078644fcca5d684775
Alexander Barkov