Am 18.01.2016 um 11:31 schrieb Martin Tschierschke:
Hi, for my first little vibe.d program, i am using
dependency "mysql-d" version="~>0.3.2"now I realized, that there are three packages offering mysql connect in the DUB package registry:
mysql-lited 0.2.23, 27 days ago 2015-Feb-24 Lightweight native MySQL/MariaDB driver
mysql-native 0.1.3, 5 months ago 2012-May-19 A native MySQL driver implementation based on Steve Teale's original
mysql-d 0.3.2, 4 months ago 2014-Jun-17 Mysql client C library binding.
I started experimenting with mysql-d from dub, because
it has the highest version number.(simply inserting:
dependency "mysql-d" version="~>0.3.2"
in dub.sdl)In the vibe.d documentation at: http://vibed.org/features#productivity
is a link to mysql-d/mysql-native forked from simendsjo/mysqln ? So please give me a hint, should I change and what to insert in sub.sdl?Thank you.
mysql-native has been around for the longest time so far, so I'd usually
recommend that (dependency "mysql-native" version="~>0.1.3"). The
version number is a bit misleading and should probably be 1.0.0 by now.
I don't know anything about mysql-lited, but from the project
description it sounds like it may have been created to be a faster
alternative to mysql-native. Maybe the author Márcio Martins sees this
to give more insight.
mysql-d is just a wrapper around the C client library and as such
doesn't support vibe.d's asynchronous I/O model. As long as the SQL
server runs on 127.0.0.1, this won't make a real difference. But as soon
as it is on a different machine, this can become a performance issue.