Package Details: mariadb-connector-c 3.0.9-1

Git Clone URL: https://aur.archlinux.org/mariadb-connector-c.git (read-only)
Package Base: mariadb-connector-c
Description: MariaDB Connector/C is used to connect applications developed in C/C++ to MariaDB and MySQL databases.
Upstream URL: https://mariadb.com/kb/en/mariadb/about-mariadb-connector-c/
Licenses: LGPL
Submitter: BluePeril
Maintainer: BluePeril
Last Packager: BluePeril
Votes: 6
Popularity: 0.001629
First Submitted: 2016-02-13 08:04
Last Updated: 2019-03-19 19:26

Latest Comments

Singularity commented on 2019-01-09 18:54

It took me really a while to figure out that libmariadbclient 10.3.x provides the same functionality, and that MariaDB Connector/C only provides only a more permissive license. It exist for people who want to ship it with their self-writen application.

There are two scenarios where you want to install this package:

  • you want a newer version than libmariadbclient 10.1.x from the repo provides. (*)

  • you don't want to install the mariadb terminal client, and the database to which you connect is remote.

(*): It can be installed with the mariadb version form the repos because they are compiled with -DINSTALL_PLUGINDIR=lib/mysql/plugin -DINSTALL_INCLUDEDIR=include/mysql. I don't know if the headers and plugins from the mariadb or mysql subdirectories will be used. But one could work around it by using NoExtract = usr/include/mysql/ in /etc/pacman.conf

kleest commented on 2018-07-20 19:24

MYSQL_UNIX_ADDR CMake variable has been renamed to MARIADB_UNIX_ADDR in upstream commit 28edd6d18edbc51498f2320f18280feb1103b087.

dotted commented on 2018-02-24 01:02

Integrity check fails for 3.0.3

jamespharvey20 commented on 2016-09-28 02:23

The mariadb package defaults to placing its socket at /run/mysqld/mysqld.sock

Upstream's mariadb-connector-c defaults to looking for it at /tmp/mysql.sock

This is fixed by adding to PKGBUILD's cmake call:
-DMYSQL_UNIX_ADDR=/run/mysqld/mysqld.sock \

(There's of course work-arounds such as a symlink (if nothing removes it) or putting the correct socket location in every mysql_init call.)