Chriscalender.com Website Review

tips and solutions for mysql®, mariadb®, and other mysql-related topics i just wanted to provide quick tutorial on using mariadb’s connector c. i do*nloaded the latest connector c (3.0.2), running mariadb 10.1.28, and was able to get it to work fine with a simple c program using the 1. do*nloaded the connector c .msi file (32-bit, since my vs is 32-bit), extracted, and installed, which placed it at: 2. you need to add the directory that contains libmaria.dll to your $path environment lib path variable. in my case, it was: note the first path is to include all normal c headers like stdio.h, the second for mysql.h, and the third is for windows.h, and the last microsoft (r) incremental linker version 10.00.40219.01 copyright (c) microsoft corporation. all rights reserved.. an introduction to mariadb’s data at rest encryption (dare) – part 2. on enabling mariadb’s data at rest encryption, and now you are ready to create an encrypted table. and just to get it out of the way for those interested, you can always check your encrypted (and non-encrypted) table stats via: i find the following 4 tables interesting, as the first 3 essentially all create the same table, and the 4th shows how to create a create table t10 (id int) engine=innodb; create table t11 (id int) engine=innodb encrypted=yes; so when configuered as above, then we see t10, t11, and t12 were all encrypted no matter whether we specified encrypted=yes in the create we see that t13 was not encrypted, since we did specify encrypted=no in the create table. this is possible when you use. let’s encrypt a non-encrypted table (t13) to be encrypted: mariadb> alter table t13 encrypted=yes; query ok, 0 rows affected (0.16 sec). now let’s perform the reverse, un-encrpyt an encrypted table: mariadb> alter table t13 encrypted=no; query ok, 0 rows affected (0.19 sec) with this setting, if you attempt to create a table with encrypted=no, then the command will fail: