Fixed
Status Update
No update yet.
Comments
yb...@google.com
fl...@google.com
ap...@google.com
We'd also need to trim the ")".
fl...@google.com
mi...@gmail.com
that would not work because we don't know if the IN statement is a positive one or a negative one.
e.g. the result would be different if it is
NOT IN
vs
IN.
but putting () should just do the right thing. afaik, SQLite accepts empty set.
e.g. the result would be different if it is
NOT IN
vs
IN.
but putting () should just do the right thing. afaik, SQLite accepts empty set.
fe...@gmail.com
When I tested empty sets I was getting no results, but let me double check that I didn't goof something.
fe...@gmail.com
i think that is WAI.
Imagine you have a query like:
@Query("select * from users where uid IN (:uids)")
List<User> getUsersByIds(List<String> uids)
If you call that query w/ an empty list of uids, the expected result should be an empty list of users.
Imagine you have a query like:
@Query("select * from users where uid IN (:uids)")
List<User> getUsersByIds(List<String> uids)
If you call that query w/ an empty list of uids, the expected result should be an empty list of users.
Description
Version used: 1.1.0
Devices/Android versions reproduced on: All
When we are working with Room database that contains predefined data, we can populate these predefined data when first creation of the database via Callback#onCreate(SupportSQLiteDatabase). If that project decided to fallback to destructive migration, all the predefined data will be delete during the migration and there is no way to notify if that happens so we can insert those predefined data.
My suggestion would be adding a new callback method e.g. onDestructiveMigrate(SupportSQLiteDatabase). Then notify the callback once migrated by destruction.