IssueTracker

I think it is best if we implement the following:

3.1. Determination Of Column Affinity
The affinity of a column is determined by the declared type of the column, according to the following rules in the order shown:

If the declared type contains the string "INT" then it is assigned INTEGER affinity.

If the declared type of the column contains any of the strings "CHAR", "CLOB", or "TEXT" then that column has TEXT affinity. Notice that the type VARCHAR contains the string "CHAR" and is thus assigned TEXT affinity.

If the declared type for a column contains the string "BLOB" or if no type is specified then the column has affinity BLOB.

If the declared type for a column contains any of the strings "REAL", "FLOA", or "DOUB" then the column has REAL affinity.

Otherwise, the affinity is NUMERIC.

Note that the order of the rules for determining column affinity is important. A column whose declared type is "CHARINT" will match both rules 1 and 2 but the first rule takes precedence and so the column affinity will be INTEGER.

Can you please specify from which release this issue has been fixed? Thanks!

I've posted a migration solution here: https://stackoverflow.com/questions/48261997/room-migration-using-existing-boolean-column-types/55304942#55304942

I believe this is still an issue with Room 2.2.1? I am still getting issues like the following:

Expected:

TableInfo{name='planets', columns={name=Column{name='name', type='TEXT', affinity='2', notNull=true, primaryKeyPosition=0, defaultValue='null'}, rebel_base_lat=Column{name='rebel_base_lat', type='INTEGER', affinity='3', notNull=true, primaryKeyPosition=0, defaultValue='null'}, id=Column{name='id', type='INTEGER', affinity='3', notNull=true, primaryKeyPosition=1, defaultValue='null'}, rebel_base_lon=Column{name='rebel_base_lon', type='INTEGER', affinity='3', notNull=true, primaryKeyPosition=0, defaultValue='null'}}, foreignKeys=[], indices=[]}
     

Found:

TableInfo{name='planets', columns={rebel_base_lat=Column{name='rebel_base_lat', type='decimal', affinity='1', notNull=false, primaryKeyPosition=0, defaultValue='null'}, name=Column{name='name', type='varchar(255)', affinity='2', notNull=false, primaryKeyPosition=0, defaultValue='null'}, id=Column{name='id', type='integer', affinity='3', notNull=false, primaryKeyPosition=1, defaultValue='null'}, rebel_base_lng=Column{name='rebel_base_lng', type='decimal', affinity='1', notNull=false, primaryKeyPosition=0, defaultValue='null'}}, foreignKeys=[], indices=[]}

I forgot to mention in the previous comment: this issue happens when using the "createFromAsset" functionality as described in [1]. I am trying to get the data from an existing sqlite database.

[1] https://medium.com/androiddevelopers/packing-the-room-pre-populate-your-database-with-this-one-method-333ae190e680

My apologies for the misleading report. After debugging I found out that the reason was a typo in one of my columns plus the use of not nullable types in my Kotlin entity. This means that createFromAsset seems to work fine, but it necessary to make sure that the types, nullability and default values match.