Creating a table named 'Transaction' causes migration issue on iOS

[dcoletto]

An SQL statement like CREATE TABLE transaction (...); will lead to migration issue at runtime on iOS only. Renaming the table fixed the issue, table fields are not related.

Personal supposition here, which could be totally wrong:
I think that the issue is caused by the fact that swift (maybe even objc, I can't remember this) doesn't have the package structure which java has. Since there is already a class called Transaction in sqldelight (the one for handling db transaction) creating a table named transaction will lead to the creation of another class with the same name, and this could probably cause this strange behaviour.
Having the gradle plugin checking for tables with this name and blocking this issue at compile time would be nice, even if you are not working on K/N (so if one day you decide to move your android project on iOS you won't have the issue)