I've been working on a big refresh of mysql-native's API, to take care of various issues that have appeared with it. It involves some major breaking changes (although I've tried to keep old interfaces around for the moment, but marked deprecated), so I wanted to post it before committing to it so those interested have a change to take a look, give feedback, catch problems, etc.

Summary of these changes:

API overhauled for better safety, reliability and ease-of-use. Deprecated and replaced entire Command struct with better design. Better handling of null. Various bugs fixed and more rigorously tested.

------

For right now, the changes are in a separate fork, here:

https://github.com/Abscissa/mysql-native-experimental

The readme there has sample code and an overview of the new interface.

Changelog: https://github.com/Abscissa/mysql-native-experimental/blob/master/CHANGELOG.md

API ref: http://semitwist.com/mysql-native-docs/v0.2.0-preview1

-------

So take a look, let me know if there's any big issues with it. If all looks good, this will soon be released as mysql-native v0.2.0.

Am 30.01.2017 um 03:56 schrieb Nick Sabalausky:
> (...)
>
> So take a look, let me know if there's any big issues with it. If all
> looks good, this will soon be released as mysql-native v0.2.0.

What about directly going for 1.0.0? At least after it has gotten enough real-world exposure, I'd say that the first API overhaul is a good opportunity for that.

Wow :) Maybe it is time to go back from mysql-lited to mysql-native :)


Dne 30.1.2017 v 03:56 Nick Sabalausky via Digitalmars-d-announce napsal(a):
> I've been working on a big refresh of mysql-native's API, to take care of various issues that have appeared with it. It involves some major breaking changes (although I've tried to keep old interfaces around for the moment, but marked deprecated), so I wanted to post it before committing to it so those interested have a change to take a look, give feedback, catch problems, etc.
>
> Summary of these changes:
>
> API overhauled for better safety, reliability and ease-of-use. Deprecated and replaced entire Command struct with better design. Better handling of null. Various bugs fixed and more rigorously tested.
>
> ------
>
> For right now, the changes are in a separate fork, here:
>
> https://github.com/Abscissa/mysql-native-experimental
>
> The readme there has sample code and an overview of the new interface.
>
> Changelog: https://github.com/Abscissa/mysql-native-experimental/blob/master/CHANGELOG.md
>
> API ref: http://semitwist.com/mysql-native-docs/v0.2.0-preview1
>
> -------
>
> So take a look, let me know if there's any big issues with it. If all looks good, this will soon be released as mysql-native v0.2.0.

On Monday, 30 January 2017 at 02:56:27 UTC, Nick Sabalausky wrote:
> I've been working on a big refresh of mysql-native's API, to take care of various issues that have appeared with it. It involves some major breaking changes (although I've tried to keep old interfaces around for the moment, but marked deprecated), so I wanted to post it before committing to it so those interested have a change to take a look, give feedback, catch problems, etc.

Nice!

On Monday, 30 January 2017 at 02:56:27 UTC, Nick Sabalausky wrote:
> I've been working on a big refresh of mysql-native's API, to take care of various issues that have appeared with it. It involves some major breaking changes (although I've tried to keep old interfaces around for the moment, but marked deprecated), so I wanted to post it before committing to it so those interested have a change to take a look, give feedback, catch problems, etc.

It is all really nice, but I think it would be nice to have an API that is as close to the C API as possible, for those developers out there familiar with the MySQL C API.

Dne 30.1.2017 v 10:14 Dejan Lekic via Digitalmars-d-announce napsal(a):

> On Monday, 30 January 2017 at 02:56:27 UTC, Nick Sabalausky wrote:
>> I've been working on a big refresh of mysql-native's API, to take care of various issues that have appeared with it. It involves some major breaking changes (although I've tried to keep old interfaces around for the moment, but marked deprecated), so I wanted to post it before committing to it so those interested have a change to take a look, give feedback, catch problems, etc.
>
> It is all really nice, but I think it would be nice to have an API that is as close to the C API as possible, for those developers out there familiar with the MySQL C API.
No. Why? It does not make sense, almost nobody use C API directly. Everybody I know use some library build around C API.

On Monday, 30 January 2017 at 02:56:27 UTC, Nick Sabalausky wrote:
> I've been working on a big refresh of mysql-native's API, to take care of various issues that have appeared with it. It involves some major breaking changes (although I've tried to keep old interfaces around for the moment, but marked deprecated), so I wanted to post it before committing to it so those interested have a change to take a look, give feedback, catch problems, etc.
>
> [...]

Can we use semantic versioning correctly here and get an increment on the major version please. I'm so sick of seeing D libs in endless alpha/beta!

On Monday, 30 January 2017 at 08:09:18 UTC, Daniel Kozak wrote:
> Wow :) Maybe it is time to go back from mysql-lited to mysql-native :)

I doubt that. Mysql-lited has support for using a struct as a Schema for DB queries. The @as and @optional properties are so useful for project I'm working on.

Unless mysql-native has that.

Dne 30.1.2017 v 10:53 aberba via Digitalmars-d-announce napsal(a):

> On Monday, 30 January 2017 at 08:09:18 UTC, Daniel Kozak wrote:
>> Wow :) Maybe it is time to go back from mysql-lited to mysql-native :)
>
> I doubt that. Mysql-lited has support for using a struct as a Schema for DB queries. The @as and @optional properties are so useful for project I'm working on.
>
> Unless mysql-native has that.
I do not use any of these  :)

On 01/30/2017 02:49 AM, Sönke Ludwig wrote:
>
> What about directly going for 1.0.0? At least after it has gotten enough
> real-world exposure, I'd say that the first API overhaul is a good
> opportunity for that.

Good point.