Fixed
Status Update
Comments
da...@google.com <da...@google.com>
el...@google.com <el...@google.com>
ap...@google.com <ap...@google.com> #2
For one of observables (single, maybe) we don't specify a subscvription thread so that developer can control where the action happens.
For flowables / observables; we always use the Room IO thread fo rthe actual query since we may repeat the work.
For LiveData, ti si always the Room IO Thread.
Until we can extend Room Query methods to receive non-query parameter (e.g. a Scheduler) we cannot do this.
At least room catches this instantly since it will crash w/ db access on main thread exception.
For flowables / observables; we always use the Room IO thread fo rthe actual query since we may repeat the work.
For LiveData, ti si always the Room IO Thread.
Until we can extend Room Query methods to receive non-query parameter (e.g. a Scheduler) we cannot do this.
At least room catches this instantly since it will crash w/ db access on main thread exception.
Description
Component
Description
Adding column name with SQL keyword makes the compiler fail to escape the keyword and thereafter fail to migrate the database.
I seem to be unable to escape this even with the
RenameColumn
andDeleteColumn
as they seek the exact names and therefore will skip escaping with `.Proposed Solution
Have the compiler escape SQL keywords in column and table names.
Code sample
Before:
After: