elenst

MariaDB [test]> create function json_get_item returns string soname 'ha_connect.so';
Query OK, 0 rows affected (0.02 sec)

MariaDB [test]> select json_get_item('{"id": 1}', 'id:*');
+------------------------------------+
| json_get_item('{"id": 1}', 'id:*') |
+------------------------------------+
| NULL                               |
+------------------------------------+
1 row in set (0.00 sec)

elenst

2017-06-22 23:18:52 140533309737728 [Note] /data/bld/10.1/bin/mysqld: Normal shutdown

2017-06-22 23:18:52 140533309737728 [Note] Event Scheduler: Purging the queue. 0 events
2017-06-22 23:18:52 140532617561856 [Note] InnoDB: FTS optimize thread exiting.
2017-06-22 23:18:52 140533309737728 [Note] InnoDB: Starting shutdown...
2017-06-22 23:18:52 140533309737728 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
2017-06-22 23:18:54 140533309737728 [Note] InnoDB: Shutdown completed; log sequence number 1616829
2017-06-22 23:18:54 140533309737728 [Note] /data/bld/10.1/bin/mysqld: Shutdown complete

elenst

DELIMITER $
CREATE PROCEDURE pr_create()
BEGIN
  DECLARE i INT DEFAULT 0;
  WHILE i < 3000
  DO
    SET @sql = CONCAT('CREATE TABLE t', i, ' (i INT)');
    PREPARE stmt FROM @sql;
    EXECUTE stmt;
    DEALLOCATE PREPARE stmt;

elenst

2017-06-01  7:57:25 10564 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-06-01  7:57:25 10564 [Note] InnoDB: Uses event mutexes
2017-06-01  7:57:25 10564 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-06-01  7:57:25 10564 [Note] InnoDB: Number of pools: 1
2017-06-01  7:57:25 10564 [Note] InnoDB: Using generic crc32 instructions
2017-06-01  7:57:25 10564 [Note] InnoDB: Initializing buffer pool, total size = 16G, instances = 8, chunk size = 128M
2017-06-01  7:57:26 10564 [Note] InnoDB: Completed initialization of buffer pool
2017-06-01  7:57:26 10564 [Note] InnoDB: Highest supported file format is Barracuda.
2017-06-01  7:57:26 10564 [Note] InnoDB: S: (0x01000609000E0B020D01070D0A0D06020D0E0C040D09040009010D0E070206070C0D0A0E0C04040B0C0C050905010203010F01030601060A0101090D020B010F070108030502040A0F0206070C0202010900000E0C030C020
70D000A090902070F07050402030B090B020702070A0A090E0E0C060B010F0A080B0008020D080A09050D0009020F0A0300090903020A060203040B0D0600020A0905010C01000700080601

elenst

fuzzy_formula='
   rounded = 0;
   if (fuzzy_var <= 10 ) {
      rounded   = 1;
   }
   factor = 1;
   while ( rounded == 0 ) {
      if ( fuzzy_var <= 50 * factor ) {
         fuzzy_var = sprintf("%.0f", fuzzy_var / (5 * factor)) * 5 * factor;
         rounded   = 1;

elenst

Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!Item_func_trig_cond::val_int()[item_cmpfunc.h:609]
mysqld.exe!Item::val_bool()[item.cc:112]
mysqld.exe!Item_cond_and::val_int()[item_cmpfunc.cc:4972]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3341]
mysqld.exe!JOIN::exec()[sql_select.cc:3267]
mysqld.exe!st_select_lex_unit::exec()[sql_union.cc:989]
mysqld.exe!subselect_union_engine::exec()[item_subselect.cc:3845]

elenst

client-core-10.3

Depends: libmariadb3 (>= 10.3.0+maria~xenial), mariadb-common (>= 10.3.0+maria~xenial), libc6 (>= 2.17), libncurses5 (>= 6), libreadline5 (>= 5.2), libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 4.1.1), libtinfo5 (>= 6), zlib1g (>= 1:1.1.4)
 Conflicts: mariadb-client-10.0, mariadb-client-10.1, mariadb-client-5.1, mariadb-client-5.2, mariadb-client-5.3, mariadb-client-5.5, mariadb-client-core-10.0, mariadb-client-core-10.1, mariadb-client-core-5.1, mariadb-client-core-5.2, mariadb-client-core-5.3, mariadb-client-core-5.5, mysql-client (<< 5.0.51), mysql-client-5.0, mysql-client-5.1, mysql-client-5.5, mysql-client-core-5.1, mysql-client-core-5.5, mysql-client-core-5.6, mysql-client-core-5.7, virtual-mysql-client-core
 Replaces: mariadb-client-10.0, mariadb-client-10.1, mariadb-client-5.1, mariadb-client-5.2, mariadb-client-5.3, mariadb-client-5.5, mariadb-client-core-10.0, mariadb-client-core-10.1, mariadb-client-core-5.1, mariadb-client-core-5.2, mariadb-client-core-5.3, mariadb-client-core-5.5, mysq

elenst

10.2 238c6700dd52

bld-dan-debug (dan_demeter2)
bld-dan-release (dan_demeter2)
- compile : Could NOT find GnuTLS

kvm-bintar-centos5-x86
kvm-deb-wheezy-x86 
kvm-fulltest2
labrador

elenst

> Debug.ListCallStack /AllThreads /ShowExternalCode:no
Callstack for Thread 1 (Thread Id: 3516 (0xdbc)):
 Index  Function
--------------------------------------------------------------------------------
 1      [External Code]
 2      mysqld.exe!pthread_cond_timedwait(_RTL_CONDITION_VARIABLE * cond=0x00007ff713ca99e8, _RTL_CRITICAL_SECTION * mutex=0x00007ff713ca7b00, const timespec * abstime=0x0000000000000000)
 3      mysqld.exe!pthread_cond_wait(_RTL_CONDITION_VARIABLE * cond=0x00007ff713ca99e8, _RTL_CRITICAL_SECTION * mutex=0x00007ff713ca7b00)
 4      mysqld.exe!inline_mysql_cond_wait(st_mysql_cond * that=0x00007ff713ca99e8, st_mysql_mutex * mutex=0x00007ff713ca7b00, const char * src_file=0x00007ff711f62490, unsigned int src_line=5551)
 5      mysqld.exe!handle_connections_methods()
 6      mysqld.exe!win_main(int argc=44, char * * argv=0x0000002e1aef3a98)

elenst

MariaDB [test]> create table t20 (pk int primary key, a int, key GEN_CLUST_INDEX(a)) engine=innodb;
ERROR 1280 (42000): Incorrect index name 'GEN_CLUST_INDEX'
MariaDB [test]> show warnings;
+---------+------+-------------------------------------------------------------------------------------------------------------+
| Level   | Code | Message                                                                                                     |
+---------+------+-------------------------------------------------------------------------------------------------------------+
| Warning | 1280 | Cannot Create Index with name 'GEN_CLUST_INDEX'. The name is reserved for the system default primary index. |
| Error   | 1280 | Incorrect index name 'GEN_CLUST_INDEX'                                                                      |
| Warning | 1030 | Got error -1 "Internal error < 0 (Not system error)" from storage engine InnoDB                             |
+---------+------+------------------------------------------