Re: [Sqlalchemy-tickets] [sqlalchemy] #2841: MySQL doesn't support MATCH, INITIALLY, or DEFERRED

[sqlalchemy <mi...@zz...>]

#2841: MySQL doesn't support MATCH, INITIALLY, or DEFERRED
---------------------------+----------------------------------
      Reporter:  uijllji   |      Owner:  zzzeek
          Type:  defect    |     Status:  new
      Priority:  high      |  Milestone:  0.8.xx
     Component:  mysql     |   Severity:  minor - half an hour
    Resolution:            |   Keywords:  mysql, ddl, schema
Progress State:  in queue  |
---------------------------+----------------------------------
Changes (by zzzeek):

 * priority:  medium => high
 * milestone:   => 0.8.xx
 * component:  cextensions => mysql
 * severity:  no triage selected yet => minor - half an hour
 * status_field:  awaiting triage => in queue


Comment:

 So I'm torn between CompileError and warning with or without ignoring it.
 someone who wants to set up MATCH for other backends would otherwise have
 to do a conditional DDL here, but if someone actually needs MATCH to be
 significant probably has to do that anyway.

 how about CompileError on 0.9 and warning on 0.8?   it is possible
 existing applications are relying upon current behavior.

--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2841#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python