digitalmars.D.announce - mysql-native v2.0.0-rc1: Release Candidate: Redesigned Prepared
- Nick Sabalausky (Abscissa) (18/18) Feb 04 2018 An all-D MySQL/MariaDB client library:
- aberba (5/8) Feb 06 2018 I really want to thank you for putting much time into
- Nick Sabalausky (Abscissa) (5/8) Feb 06 2018 Glad to hear! Boring as documenting can be, my viewpoint is that it's
- Nick Sabalausky (Abscissa) (4/4) Feb 06 2018 Second release candidate: Tagged v2.0.0-rc2
- bauss (5/25) Feb 08 2018 Been waiting for this!
- Nick Sabalausky (Abscissa) (9/9) Feb 08 2018 Hopefully the last.
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 2018
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 2018
"Nick Sabalausky (Abscissa)" <SeeWebsiteToContactMe semitwist.com> 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 2018
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 2018
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/issuesBeen 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 2018
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 2018