From: Ruben Perez (rubenperez038_at_[hidden])
Date: 2022-06-14 22:36:01
Hi all,
We have received an answer from Oracle's legal
team, thanks to Norvald, who initially wrote
in this ML and works for Oracle.
TL;DR: Boost.MySQL keeps its name.
> Naming the library as proposed (Boost.MySQL) is not a problem for a
> community connector to MySQL. This is consistent with other naming we
> see in the MySQL community and in our experience it has not caused
> confusion. We would be concerned about any naming or statements that
> suggest an inaccurate association between your library or product and
> MySQL, but that does not appear to be the case.
So I'm afraid we won't be having Boost.OurSQL anytime soon.
Regards,
Ruben.