Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
MySQL++ is a C++ wrapper for MySQL’s C API. It is built around the same principles as the Standard C++ Library, to make dealing with the database as easy as dealing with STL containers. In addition, MySQL++ provides facilities that let you avoid the most repetitive sorts of SQL within your own code, providing native C++ interfaces for these common tasks.
If you have questions about this project and can’t find an answer in the documentation or the mailing list archives, ask on the web forum or the mailing list. We also have a ticket system, but it's best to discuss such things first before filing a ticket.
Before upgrading an existing version of MySQL++, please scan through the change log first. If you’re coming from a much older version, better read through the “Incompatible Library Changes” chapter in the user manual instead.
The MySQL++ source code is available in several forms:
Release Tarball: mysql++-3.2.5.tar.gz (4.5 MiB, 2019.07.21) — If you aren’t sure which file to download, download this.
Release SRPM: mysql++-3.2.5-1.el7.src.rpm (3.3 MiB, 2019.07.21) — For those that need to build their own binary RPMs:
$ rpmbuild --rebuild /wherever/it/is/mysql++-3.2.5-1.el7.src.rpm
mysql++-manualsRPMs should then be found in
~/rpmbuild/RPMS/x86_64if you did it on a 64-bit x86 based Linux box.
Tip-of-trunk Tarball: mysql++-trunk.tar.gz — For those who need the latest bleeding-edge version without bothering with Fossil. This is "stable" in the sense that our repository trunk almost always compiles and runs; experimental work is done on branches to avoid destabilizing trunk.
Fossil Repository: You may clone our Fossil repository to get the current work on MySQL++ with abridged history going back to the project's founding, the wiki contents, our ticket tracker contents, forum posts, and more. The repository is well-tagged, so you can compare versions, roll back to old versions, etc. This is the best option for those who want to participate in the development of MySQL++.
MySQL++ has been picked up by many package distros. It’s been spotted in the Debian, Fedora, FreeBSD, Gentoo, Homebrew, RHEL (EPEL), and Ubuntu package systems. Since these packages are properly integrated into their host distributions, we no longer offer competing binary packages here.
If you want something different in your binary package than you get in the standard package distro for your OS, you should build it from source on the target OS, or else you are likely to have problems.
Those still needing MySQL++ 2.x might be interested in the
v2.3.2-modern branch, which makes minimal changes to version 2.3.2 — the last release in the 2.x line — to allow it to build on modern systems. Essentially, it contains build fixes analogous to those we've done in the 3.x line without backporting any actual features or behavior changes from 3.x. This branch is unlikely to ever be released, but it is intended to be "stable" at all times.
The user and reference manuals are shipped in the source code tarball above. They are also available online.
The FAQ list answers many commonly-asked questions about MySQL++.
The easiest thing to do if you want to help out with the MySQL++ development effort is to participate on the mailing list and/or web forum. The library's primary developer does not mind at all if someone else answers a question before he can get to it. :) It’s also frequently helpful to have different voices contributing to discussions about the library’s future.
If you want to participate in the coding effort, the MySQL++ development project is hosted by Fossil, a distributed version control similar to Git but much easier to use. See the Hackers file for instructions on working with Fossil and the MySQL++ source code.
For a great source of projects to tackle, see the Wishlist.
If you just want to keep up on the in-progress developments, see the project timeline, which is also available in RSS form for those who want MySQL++ changes to appear in their feed reader. You can also subscribe to email notifications for various events: check-ins, wiki edits, forum postings, etc.