The mysql-native package is a native all-D client library for MySQL and MariaDB. If vibe-d is included in your project, it will use vibe-d networking, otherwise it will use Phobos networking.

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

In this update, mysql-native's vibe-d support has switched from the old `vibe-d:core` package to the new `vibe-core` package. Several other improvements are included as well. See the changelog for details: < https://github.com/mysql-d/mysql-native/blob/master/CHANGELOG.md >. Big thanks to @SingingBush and @schveiguy for their contributions in this release.

On the near horizon, work on v3.1.0 and v4.0.0 is already well underway which will make much of mysql-native @safe. This is necessitating a change away from using Phobos's Variant for data, but we think this will be well worth it as the new replacement offers a much nicer API. And of course, effort is being made to make migrating go as smoothly and simply as possible.

On Sunday, 8 December 2019 at 23:35:02 UTC, Nick Sabalausky (Abscissa) wrote:
> The mysql-native package is a native all-D client library for MySQL and MariaDB. If vibe-d is included in your project, it will use vibe-d networking, otherwise it will use Phobos networking.
>
> https://github.com/mysql-d/mysql-native
>
> In this update, mysql-native's vibe-d support has switched from the old `vibe-d:core` package to the new `vibe-core` package. Several other improvements are included as well. See the changelog for details: < https://github.com/mysql-d/mysql-native/blob/master/CHANGELOG.md >. Big thanks to @SingingBush and @schveiguy for their contributions in this release.
>
> On the near horizon, work on v3.1.0 and v4.0.0 is already well underway which will make much of mysql-native @safe. This is necessitating a change away from using Phobos's Variant for data, but we think this will be well worth it as the new replacement offers a much nicer API. And of course, effort is being made to make migrating go as smoothly and simply as possible.

Cool, thank you!

Is there a easy way to get the mysql row as an AA?
So that I can write something like result["email"] if "email" is a column?

I just saw this:
>> New: #188: Expose column names in Row struct via Row.getName(index). (@jpf91)
Should I use this? And just fill an AA myself?


In the moment I am using this feature with mysql-d and would like to switch to a better maintained package.

On 12/9/19 6:02 AM, Martin Tschierschke wrote:

> Is there a easy way to get the mysql row as an AA?
> So that I can write something like result["email"] if "email" is a column?

ResultRange has an asAA member which does what you want.

> I just saw this:
>>> New: #188: Expose column names in Row struct via Row.getName(index). (@jpf91)
> Should I use this? And just fill an AA myself?

I don't know why the asAA isn't in Row. I didn't actually realize the Row now had access to the column names.

-Steve

On Monday, 9 December 2019 at 16:15:50 UTC, Steven Schveighoffer wrote:
> On 12/9/19 6:02 AM, Martin Tschierschke wrote:
>
>> Is there a easy way to get the mysql row as an AA?
>> So that I can write something like result["email"] if "email" is a column?
>
> ResultRange has an asAA member which does what you want.
Oh, that's great!
Thank you!