www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.announce - mysql-native v2.0.0-rc1: Release Candidate: Redesigned Prepared

reply "Nick Sabalausky (Abscissa)" <SeeWebsiteToContactMe semitwist.com> writes:
An all-D MySQL/MariaDB client library:

https://github.com/mysql-d/mysql-native

------------------------------

I've tagged a release candidate ("v2.0.0-rc1") which, among other 
various enhancements and cleanups, includes a redesign of prepared 
statements which are now connection-independent (among other benefits).

If you use prepared statements, this *does* involve some small breaking 
changes. A migration guide is provided here:

https://github.com/mysql-d/mysql-native/blob/master/MIGRATING_TO_V2.md


Motivations and the specific changes for prepared statements are 
explained here:

https://github.com/mysql-d/mysql-native/blob/master/ABOUT_PREPARED_V2.md

------------------------------

Full list of all other changes in this release in the changelog:

https://github.com/mysql-d/mysql-native/blob/master/CHANGELOG.md

------------------------------

Please give it a try and let me know how it works out. Please file any 
issues here: https://github.com/mysql-d/mysql-native/issues
Feb 04
next sibling parent reply aberba <karabutaworld gmail.com> writes:
On Monday, 5 February 2018 at 04:47:07 UTC, Nick Sabalausky 
(Abscissa) wrote:
 An all-D MySQL/MariaDB client library:

 https://github.com/mysql-d/mysql-native

 [...]
I really want to thank you for putting much time into documentation. Very much appreciated. This library is very necessary for the stuff I do.
Feb 06
parent "Nick Sabalausky (Abscissa)" <SeeWebsiteToContactMe semitwist.com> writes:
On 02/06/2018 03:42 AM, aberba wrote:
 
 I really want to thank you for putting much time into documentation. 
 Very much appreciated. This library is very necessary for the stuff I do.
Glad to hear! Boring as documenting can be, my viewpoint is that it's every bit as integral to a tool as the code itself: If people don't know how to use something, then what good does it do for it to exist at all? (Plus it helps me remember later on just what the heck I was doing :) )
Feb 06
prev sibling next sibling parent "Nick Sabalausky (Abscissa)" <SeeWebsiteToContactMe semitwist.com> writes:
Second release candidate: Tagged v2.0.0-rc2

Changes since RC1 listed in changelog:
https://github.com/mysql-d/mysql-native/blob/master/CHANGELOG.md

These changes are needed to help prepare for the eventual v2.1.0
Feb 06
prev sibling next sibling parent bauss <jj_1337 live.dk> writes:
On Monday, 5 February 2018 at 04:47:07 UTC, Nick Sabalausky 
(Abscissa) wrote:
 An all-D MySQL/MariaDB client library:

 https://github.com/mysql-d/mysql-native

 ------------------------------

 I've tagged a release candidate ("v2.0.0-rc1") which, among 
 other various enhancements and cleanups, includes a redesign of 
 prepared statements which are now connection-independent (among 
 other benefits).

 If you use prepared statements, this *does* involve some small 
 breaking changes. A migration guide is provided here:

 https://github.com/mysql-d/mysql-native/blob/master/MIGRATING_TO_V2.md


 Motivations and the specific changes for prepared statements 
 are explained here:

 https://github.com/mysql-d/mysql-native/blob/master/ABOUT_PREPARED_V2.md

 ------------------------------

 Full list of all other changes in this release in the changelog:

 https://github.com/mysql-d/mysql-native/blob/master/CHANGELOG.md

 ------------------------------

 Please give it a try and let me know how it works out. Please 
 file any issues here: 
 https://github.com/mysql-d/mysql-native/issues
Been waiting for this! Thank you for all your effort. Going to test it out later and see how it works compared to now.
Feb 08
prev sibling parent "Nick Sabalausky (Abscissa)" <SeeWebsiteToContactMe semitwist.com> writes:
Hopefully the last.

Changes since RC2 listed in changelog:
https://github.com/mysql-d/mysql-native/blob/master/CHANGELOG.md

------------------------------

Incidentally, when you're sticking to semantic versioning, utilizing 
release candidates and git branches REALLY comes in handy ;)  Highly 
recommend. Work on v2.1.0 is progressing while v2.0.0 is stabilizing. 
Plus, some of the work on v2.1.0 has revealed needs that are best 
included in v2.0.0 to avoid an imminent bump to v3+. Nice.
Feb 08