I couldn't see what it would actually, seriously break other than different
<br>
DDL. If it causes real problems let's just revert it, rerelease, and add
<br>
deprecation cycle.
<br>
<br>
Also, fwiw I agree re not having two issue trackers. I like github but
<br>
having two trackers just blows.
<br>
On Oct 31, 2013 4:52 AM, "Peter Rabbitson" <notifications@github.com> wrote:
<br>
<br>
> In essence the change is "more correct", but even the cited docs *
<br>
> discourage* use of the AUTOINCREMENT keyword. I am not sure what the
<br>
> correct way forward is here at this point...
<br>
>
<br>
> In any case this is a grossly incompatible change, for which I *believe*we needed an at least couple month warning cycle, and a downstream CPAN
<br>
> smoke round. Now none of this is an option anymore. Ideas?
<br>
>
<br>
> —
<br>
> Reply to this email directly or view it on GitHub<https://github.com/dbsrgits/sql-translator/pull/26#issuecomment-27473286>
<br>
> .
<br>
>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href='https://github.com/dbsrgits/sql-translator/pull/26#issuecomment-27477879'>view it on GitHub</a>.<img src='https://github.com/notifications/beacon/4W3BWTo7EIi_7vx28Xzl_uOeUxBDjNYWumjU51m-gOiLBMgmzsWdFwoWA5qcdsWE.gif' height='1' width='1'></p>