On Fri, Feb 1, 2019 at 3:16 AM Sergei Golubchik wrote:
> Hi, Nikita!
>
> On Jan 30, Nikita Malyavin wrote:
> > >
> > > #define ER_NO_CONST_EXPR_IN_RANGE_OR_LIST_ERROR
> ER_NOT_CONSTANT_EXPRESSION
> > >
> > This error seems to be unused... Considering that, do You still want the
> > macro added to
Hi, Alexey!
On Jan 31, Alexey Botchkov wrote:
> > can a CHECK constraint have the same name as an existing FK?
>
> Yes, it can.
> So in this case the 'ALTER ... DROP CONSTRAINT c' drops the FOREIGN KEY. On
> the second call this ALTER
> removes the CHECK.
> How do you like that?
> I think it's o
Hi, Alexey!
Few questions first:
* can a CHECK constraint have the same name as an existing FK?
* what about UNIQUE constraint? it's also a constraint. The standard
says that DROP CONSTRAINT should work for uniques, and ALTER already
supports ADD CONSTRAINT UNIQUE (and ADD CONSTRAINT FOREIGN
Hi, Nikita!
On Jan 30, Nikita Malyavin wrote:
> >
> > #define ER_NO_CONST_EXPR_IN_RANGE_OR_LIST_ERROR ER_NOT_CONSTANT_EXPRESSION
> >
> This error seems to be unused... Considering that, do You still want the
> macro added to mysql.h?
Okay, if it's never issued, then no need to add the define.
>
Hi Vicentiu,
the patch is updated and notes are in comment:
https://github.com/MariaDB/server/pull/1127/
1. Should I support embedded server in this case, since it is supported in
`10.3`?
What else could be done =>
According to the comment in this task
https://jira.mariadb.org/browse/MDEV-14474?f
Hi Anel!
This is not a terribly bad patch, however you have forgotten the following
things:
You removed the misspelled is_check_constraint.test file, but forgot to
remove
the is_check_constraint.result file. Now we would be left with a dangling
result file. Please be more careful next time.
Yo
6 matches
Mail list logo
