← Back to team overview

maria-developers team mailing list archive

Re: c91ec05e01b: MDEV-20865 Store foreign key info in TABLE_SHARE


Hi, Aleksey!

On Jan 05, Aleksey Midenkov wrote:
> On Wed, Jan 1, 2020 at 4:07 PM Sergei Golubchik <serg@xxxxxxxxxxx> wrote:
> > On Jan 01, Aleksey Midenkov wrote:
> > > On Fri, Dec 27, 2019 at 8:22 PM Sergei Golubchik wrote:
> > > > On Dec 22, Aleksey Midenkov wrote:
> > >
> > > My concern is mostly about our plugins. Let the third-party
> > > plugins use that API, but our plugins are not restricted to it?
> >
> > Unfortunately it doesn't work that way. Third-party plugins use
> > everything that our plugins are using, because that's what plugin
> > authors are looking at and where they're copying from.
> >
> > Our plugins should be clean as much as possible, they set an
> > example.
> Okay, but what is wrong having two APIs: C and C++? Let's start
> defining one.

It means double the amount of APIs to learn for users and double the
amount of APIs to maintain for us. But not double the usage, as users
will either use C or C++ API, the total usage of both will be the same
as the usage of C API only.

So, benefits for plugins would be very slim, I don't see the point of
duplicating the API in C++.

So your methods can, perhaps, stay to be used internally, but let's keep
plugins on public APIs.

VP of MariaDB Server Engineering
and security@xxxxxxxxxxx