Verified
Status Update
No update yet.
Comments
se...@google.com
yb...@google.com
sh...@google.com
sh...@google.com
a9...@gmail.com
I should probably elaborate on that a bit more here :P. The ideal case would be that data classes written in other modules work the same when consumed. A standard data class (no secondary constructors, `val` properties) works fine when in the same module. The errors produced are also pretty confusing. They'll usually give what they read from the bytecode (constructor params called "var0" or the like) and reports missing setters for fields without names of said fields.
Description
Version used: 1.0.0-alpha8
Devices/Android versions reproduced on: Android Studio 3.0 Canary 9
An entity with indices creates different schemas on different operating systems (Windows, Linux, Mac)
When declaring an entity like
@Entity(tableName = "bookmark", indices = arrayOf(Index(value = "id", unique = true)))
the schema created shows the following create sql script on Linux and Mac
"createSql": "CREATE UNIQUE INDEX `index_bookmark_id` ON `${TABLE_NAME}` (`id`)"
and the following on Windows:
"createSql": "CREATE UNIQUE INDEX `index_bookmark_id`\nON `${TABLE_NAME}` (`id`)"
There is an additional "\n" inside on Windows (or missing on Linux) which results in consistent differences between those platforms.