mysql-native v3.2.0 - the safe update
https://forum.dlang.org/post/xozbnrpxmgxboykir...@forum.dlang.org On Tuesday, 14 February 2023 at 14:22:42 UTC, Rey Valeza wrote: On Saturday, 23 April 2022 at 05:12:30 UTC, Steven Schveighoffer wrote: [...] Hi Steve, I just want you to know that I updated the Vibe.d tutorial I wrote last year to emphasize database operations using mysql-native and is now viewable here: https://reyvaleza.gitbook.io/vibe.d-tutorial/ Thanks! Awesome tutorial. I plan to do some vibe.d tutorials soon. This will come in handy.
Re: mysql-native v3.2.0 - the safe update
On Tuesday, 14 February 2023 at 14:22:42 UTC, Rey Valeza wrote: On Saturday, 23 April 2022 at 05:12:30 UTC, Steven Schveighoffer wrote: [...] Hi Steve, I just want you to know that I updated the Vibe.d tutorial I wrote last year to emphasize database operations using mysql-native and is now viewable here: https://reyvaleza.gitbook.io/vibe.d-tutorial/ Thanks! your tutorial on vibe.d help me lot, I got error, after hours of try not able to remove,but with the help of your tutorial, finally I remove it. Thanks
Re: mysql-native v3.2.0 - the safe update
On 2/14/23 9:22 AM, Rey Valeza wrote: Hi Steve, I just want you to know that I updated the Vibe.d tutorial I wrote last year to emphasize database operations using mysql-native and is now viewable here: https://reyvaleza.gitbook.io/vibe.d-tutorial/ Nice! I see that you just import `mysql`. Have you tried with `mysql.safe`? I'm curious if it works, it should mostly just work. -Steve
Re: mysql-native v3.2.0 - the safe update
On Saturday, 23 April 2022 at 05:12:30 UTC, Steven Schveighoffer wrote: It's happened. I opened the PR over 2 years ago, and just got around to bringing it up to date in the last few days. This is a huge huge update. I've never done anything like this before, but I think it works as a drop-in replacement, while allowing you to migrate any piece you wish from unsafe code to safe code. Please let me know if there are *any* problems you find with this. See the [safe migration doc](https://github.com/mysql-d/mysql-native/blob/master/SAFE_MIGRATION.md) for more details. Note this does *not* build with dip1000, because the two underlying libraries (Phobos sockets and vibe.d) do not build as safe with dip1000. -Steve Hi Steve, I just want you to know that I updated the Vibe.d tutorial I wrote last year to emphasize database operations using mysql-native and is now viewable here: https://reyvaleza.gitbook.io/vibe.d-tutorial/ Thanks!
Re: mysql-native v3.2.0 - the safe update
On Saturday, 23 April 2022 at 05:12:30 UTC, Steven Schveighoffer wrote: It's happened. I opened the PR over 2 years ago, and just got around to bringing it up to date in the last few days. This is a huge huge update. I've never done anything like this before, but I think it works as a drop-in replacement, while allowing you to migrate any piece you wish from unsafe code to safe code. Please let me know if there are *any* problems you find with this. See the [safe migration doc](https://github.com/mysql-d/mysql-native/blob/master/SAFE_MIGRATION.md) for more details. Note this does *not* build with dip1000, because the two underlying libraries (Phobos sockets and vibe.d) do not build as safe with dip1000. -Steve Thank you! I'll give it a try.
Re: mysql-native v3.2.0 - the safe update
On Saturday, 23 April 2022 at 05:12:30 UTC, Steven Schveighoffer wrote: It's happened. I opened the PR over 2 years ago, and just got around to bringing it up to date in the last few days. This is a huge huge update. I've never done anything like this before, but I think it works as a drop-in replacement, while allowing you to migrate any piece you wish from unsafe code to safe code. Please let me know if there are *any* problems you find with this. See the [safe migration doc](https://github.com/mysql-d/mysql-native/blob/master/SAFE_MIGRATION.md) for more details. Note this does *not* build with dip1000, because the two underlying libraries (Phobos sockets and vibe.d) do not build as safe with dip1000. -Steve Awesome, thank you!
Re: mysql-native v3.2.0 - the safe update
On 4/27/22 6:15 AM, Andrea Fontana wrote: On Saturday, 23 April 2022 at 05:12:30 UTC, Steven Schveighoffer wrote: Note this does *not* build with dip1000, because the two underlying libraries (Phobos sockets and vibe.d) do not build as safe with dip1000. Dip1000 is marked as "superseded". I don't understand what the plan is. It's superseded by the implementation. Which means there's not really any description of what it represents. However, there is a -dip1000 switch, and my point was that mysql-native in @safe mode won't compile with it because there are no valid socket implementations for it. I have a PR into phobos to fix it: https://github.com/dlang/phobos/pull/8438 I'm not sure how vibe can be fixed, I haven't spent much time looking at it. -Steve
Re: mysql-native v3.2.0 - the safe update
On Saturday, 23 April 2022 at 05:12:30 UTC, Steven Schveighoffer wrote: This is a huge huge update. I've never done anything like this before, but I think it works as a drop-in replacement, while allowing you to migrate any piece you wish from unsafe code to safe code. Please let me know if there are *any* problems you find with this. Well done Steven! Note this does *not* build with dip1000, because the two underlying libraries (Phobos sockets and vibe.d) do not build as safe with dip1000. Dip1000 is marked as "superseded". I don't understand what the plan is. Andrea
Re: mysql-native v3.2.0 - the safe update
On 4/26/22 4:40 AM, bauss wrote: I owe you a beer, I can't tell you how long I've been waiting for this and it makes me really happy! Thanks! If you want to join me for beerconf this weekend, I'll drink a beer on your behalf ;) I'm super happy to get this in, it was blocking a bunch of things for me too. I'm going to probably spend the next few weeks migrating all my vibe.d project code to be @safe as much as possible. -Steve
Re: mysql-native v3.2.0 - the safe update
On Saturday, 23 April 2022 at 05:12:30 UTC, Steven Schveighoffer wrote: It's happened. I opened the PR over 2 years ago, and just got around to bringing it up to date in the last few days. This is a huge huge update. I've never done anything like this before, but I think it works as a drop-in replacement, while allowing you to migrate any piece you wish from unsafe code to safe code. Please let me know if there are *any* problems you find with this. See the [safe migration doc](https://github.com/mysql-d/mysql-native/blob/master/SAFE_MIGRATION.md) for more details. Note this does *not* build with dip1000, because the two underlying libraries (Phobos sockets and vibe.d) do not build as safe with dip1000. -Steve I owe you a beer, I can't tell you how long I've been waiting for this and it makes me really happy!
Re: mysql-native v3.2.0 - the safe update
On Saturday, 23 April 2022 at 05:12:30 UTC, Steven Schveighoffer wrote: It's happened. I opened the PR over 2 years ago, and just got around to bringing it up to date in the last few days. This is a huge huge update. I've never done anything like this before, but I think it works as a drop-in replacement, while allowing you to migrate any piece you wish from unsafe code to safe code. Please let me know if there are *any* problems you find with this. See the [safe migration doc](https://github.com/mysql-d/mysql-native/blob/master/SAFE_MIGRATION.md) for more details. Note this does *not* build with dip1000, because the two underlying libraries (Phobos sockets and vibe.d) do not build as safe with dip1000. -Steve Looks like a great effort! Well done.
mysql-native v3.2.0 - the safe update
It's happened. I opened the PR over 2 years ago, and just got around to bringing it up to date in the last few days. This is a huge huge update. I've never done anything like this before, but I think it works as a drop-in replacement, while allowing you to migrate any piece you wish from unsafe code to safe code. Please let me know if there are *any* problems you find with this. See the [safe migration doc](https://github.com/mysql-d/mysql-native/blob/master/SAFE_MIGRATION.md) for more details. Note this does *not* build with dip1000, because the two underlying libraries (Phobos sockets and vibe.d) do not build as safe with dip1000. -Steve
