On Thu, Jul 27, 2017 at 3:23 AM, ChangBo Guo wrote:
> Thanks for the follow up, maybe we need document the issue and work around
> in some place, in alembic?
So yes, there's a whole bunch implied by this:
1. SQLAlchemy knows how to reflect CHECK constraints. Since MariaDB
supports these as of 1
Thanks for the follow up, maybe we need document the issue and work around
in some place, in alembic?
2017-07-24 23:21 GMT+08:00 Michael Bayer :
> hey good news, the owner of the issue upstream found that the SQL
> standard agrees with my proposed behavior. So while this is current
> MariaDB 10
hey good news, the owner of the issue upstream found that the SQL
standard agrees with my proposed behavior. So while this is current
MariaDB 10.2 / 10.3 behavior, hopefully it will be resolved in an
upcoming release within those series. not sure of the timing though
so we may not be able to du
On Mon, Jul 24, 2017 at 10:37 AM, Doug Hellmann wrote:
> Excerpts from Michael Bayer's message of 2017-07-23 16:39:20 -0400:
>> Hey list -
>>
>> It appears that MariaDB as of version 10.2 has made an enhancement
>> that overall is great and fairly historic in the MySQL community,
>> they've made C
Excerpts from Michael Bayer's message of 2017-07-23 16:39:20 -0400:
> Hey list -
>
> It appears that MariaDB as of version 10.2 has made an enhancement
> that overall is great and fairly historic in the MySQL community,
> they've made CHECK constraints finally work. For all of MySQL's
> existenc
