Status Update
Comments
ad...@google.com <ad...@google.com>
aa...@google.com <aa...@google.com>
aa...@google.com <aa...@google.com> #2
The choices mentioned in
These choices have significant performance implications and I think they should definitely not be saved as default global values.
That leaves the option of saving them per table and I think this would just cause confusion. Some tables would open one way while other would open a different way.
st...@gmail.com <st...@gmail.com> #3
Is my use case something that you don't think is a reasonable scenario which should be supported in some way? If someone does the loop of "run code, see result, edit code, re-run code, re-check results, repeat until fixed", the database editing part is absolutely miserable. To the point that it renders the IDE feature unusable, and I opt to use the logcat or something else instead which has its own problems of course by being more limited.
aa...@google.com <aa...@google.com> #4
I think your use case is reasonable and it is supported with the caveat that if you want live updates, you need to.
What I can look into is persisting these settings in the current session. As in, when you rerun the app, Database inspector re-opens the queries that were open before.
Is this what you request is?
st...@gmail.com <st...@gmail.com> #5
Yes indeed, if it behaved the way you just described, it would be an absolute great quality of life improvement!
aa...@google.com <aa...@google.com>
an...@google.com <an...@google.com> #6
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Canary 4
- Android Gradle Plugin 8.8.0-alpha04
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
Description
DESCRIBE THE ISSUE IN DETAIL:
When I use the database inspector, I may do something like enable "Live updates", and increase the number of items I query from the default of 50 to a custom number like 1000, and I may pick a specific ordering on my tables. When I re-run the app, those options are simply gone, making me re-do those changes each time. This experience is quite frustrating and having some persistence across runs would make this experience much nicer.
STEPS TO REPRODUCE:
Android Studio Koala Feature Drop | 2024.1.2 Canary 7 Build #AI-241.17890.1.2412.11993144, built on June 20, 2024 Runtime version: 17.0.11+0-17.0.11b1207.24-11852314 aarch64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. macOS 14.5