Assigned
Status Update
No update yet.
Comments
lp...@google.com
We gave up upgrading to Room because we need to use FTS3/FTS4 virtual tables. Any plants to support it?
de...@gmail.com
Florina Muntenescu (Android developer advocate at Google) told me that FTS support will definitely NOT be in Room 1.0 final. It is postponed to an indeterminate later version.
lp...@google.com
It is possible to work with virtual tables and fts4 while using Room v1. You just need to create and access it by yourself using sql queries. Not perfect but it works for me (just did it a few days ago).
Can't wait for this feature to be in Room
Can't wait for this feature to be in Room
de...@gmail.com
If your FTS tables are separate from the rest of your model it's a viable solution. Mine are fully integrated with my model (almost all queries have JOINs with virtual tables) so it's a no-go.
Description
The current version of
PreferenceDialogFragmentCompatusesAlertDialog.BuilderinonCreateDialog. The issue with this is that an application using Material You will display an old-style Material 2 dialog in the preference screen, which is not great.The fix is pretty easy, just one line of code can be changed to use
MaterialAlertDialogBuilderinstead, but, being new to Android app development, it's not clear to me if this would pose some backward compatibility issue (I don't really understand why someone would still useAlertDialog.Builder, but it's possible I'm missing some use cases).About possible workarounds: I've stumbled on
onDisplayPreferenceDialogmethod in myPreferenceFragmentCompat, using a custom implementation ofListPreferenceDialogFragmentand friends. But this is not great.Also, this is my first time on Google's issue tracker, I apologize if I violated some etiquette I don't know about, in that case please point out how I could improve :)