I don't know if the MariaDB people have this priority, but inplementing CHECK CONSTRAINTS always was an omission in MySQL. You may specify such currently in CREATE/ALTER TABLE. but it is silently ignored.


-- Peter
-- Webyog

On Mon, Feb 9, 2015 at 6:47 AM, Jonas Oreland <jonaso@google.com> wrote:
Fyi: we have already fixed 4991 (after having quickly browsed the MDEV)...
i'll try to contribute it "shortly"

/Jonas

On Sun, Feb 8, 2015 at 3:28 PM, Kristian Nielsen <knielsen@knielsen-hq.org> wrote:
Sergei Golubchik <serg@mariadb.org> writes:

> On Jan 24, Tekang Check wrote:

>> the 2015 round of the Google Summer of Code. While looking at the projects.
>> I'm interested in Database replication and would love to do some work in

> Take a look at
>
>   https://mariadb.atlassian.net/issues/?jql=labels%3Dgsoc15
>
> and don't hesitate to ask if something isn't clear.

If you are interested in replication, I would recommend this task in
particular:

    MDEV-4991: GTID binlog indexing
    https://mariadb.atlassian.net/browse/MDEV-4991

This is an important task, as it solves a bottleneck that currently exists
when many slave servers connect to one master. And it should be interesting to
work on, I think.

 - Kristian.

_______________________________________________
Mailing list: https://launchpad.net/~maria-developers
Post to     : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing list: https://launchpad.net/~maria-developers
Post to     : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp