[DBIx-Class-Devel] [dbsrgits/sql-translator] Add index length option for MySQL (#68)

[M Conrad]

Well, to spell out the thought I had, the column of an index isn't always a column; it could be a function.  And there could be two functions of the same column, so the unique check probably needs to be removed.  And (I still didn't check this) if existing parsers are returning sql expressions as the 'field' currently, then the thing that the object returns when stringified should probably be an attribute named something like 'original_sql_expr' instead of 'name'.  Quoting the name in a producer should probably only happen if it is known to be a simple name.  And all these things probably need to be thought about now in order to make the postgres parser/producer reasonable to implement.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/dbsrgits/sql-translator/pull/68#issuecomment-1601588716
You are receiving this because you are subscribed to this thread.

Message ID: <dbsrgits/sql-translator/pull/68/c1601588716 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scsys.co.uk/pipermail/dbix-class-devel/attachments/20230621/73c2c9c7/attachment.htm>