Status Update
Comments
cc...@google.com <cc...@google.com> #2
Branch: androidx-master-dev
commit b90079595f33f58fece04026a97faa0d243acdb1
Author: Yuichi Araki <yaraki@google.com>
Date: Wed Sep 18 16:55:49 2019
Change the way to detect mismatch between POJO and query
This fixes cursor mismatch warnings with expandProjection.
Bug: 140759491
Test: QueryMethodProcessorTest
Change-Id: I7659002e5e0d1ef60fc1af2a625c0c36da0664d8
M room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt
M room/compiler/src/test/kotlin/androidx/room/processor/QueryMethodProcessorTest.kt
M room/compiler/src/test/kotlin/androidx/room/testing/TestProcessor.kt
an...@google.com <an...@google.com> #3
an...@google.com <an...@google.com> #4
Branch: androidx-master-dev
commit bdde5a1a970ddc9007b28de4aa29d60ffa588f08
Author: Yigit Boyar <yboyar@google.com>
Date: Thu Apr 16 16:47:05 2020
Re-factor how errors are dismissed when query is re-written
This CL changes how we handle errors/warnings if query is
re-written.
There was a bug in expandProjection where we would report warnings
for things that Room already fixes automatically (
The solution to that problem (I7659002e5e0d1ef60fc1af2a625c0c36da0664d8)
solved it by deferring validating of columns until after re-write
decision is made. Unfortunately, this required changing PojoRowAdapter
to have a dummy mapping until it is validating, make it hard to use
as it does have a non-null mapping which is not useful.
This CL partially reverts that change and instead rely on the log
deferring logic we have in Context. This way, we don't need to break
the stability of PojoRowAdapter while still having the ability to
drop warnings that room fixes. This will also play nicer when we
have different query re-writing options that can use more information
about the query results.
Bug: 153387066
Bug: 140759491
Test: existing tests pass
Change-Id: I2ec967c763d33d7a3ff02c1a13c6953b460d1e5f
M room/compiler/src/main/kotlin/androidx/room/log/RLog.kt
M room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt
di...@google.com <di...@google.com>
le...@google.com <le...@google.com>
cc...@google.com <cc...@google.com> #5
This appears to have regressed in Iguana.
We added the @Language("sql") API functionality in macrobench in this change:
So as of March 6 last year, it was working as I developed that change. I tried a few versions of Studio to narrow this regression down:
- Electric eel (not working, presumably not supported yet)
- Flamingo (works in basic way, see 1st screenshot) - I expect AndroidX would have been on a Flamingo canary when I added the annotation
- Giraffe (works)
- Hedgehog (works better, see 2nd screenshot which now highlights the table name as a standard identifier)
- Iguana (broken in current way, see 3rd screenshot)
I tested by creating a trivial empty project, and adding the following to the example unit test:
fun sql(@Language("sql") param: String) {}
@Test
fun foo() {
sql("select * from whatever")
}
Paste containing exact versions I tested on (these are just the initial stable versions of each release):
le...@google.com <le...@google.com>
di...@google.com <di...@google.com>
am...@google.com <am...@google.com> #6
The above shows the string as a syntax error, when in reality we should just be displaying it as a normal string without any syntax highlighting
That has been fixed. DeviceSpecInjector
should only be applied for @Preview
annotations. The scenario from
am...@google.com <am...@google.com> #8
Can we get that @Language("sql") support added back to Studio?
Would using @Language("RoomSql")
work for your use case? Otherwise I'll file a feature request to the core editor team to add support for @Language("sql")
and we can follow up there. I'd leave this bug focused on the issue originally reported (syntax error), which was caused by our custom device spec.
am...@google.com <am...@google.com> #10
Marking this as fixed per @Language("sql")
if this is still needed.
cc...@google.com <cc...@google.com> #11
Would using @Language("RoomSql") work for your use case
Unfortunately no, "RoomSql" doesn't support includes or function declarations in my testing (see screenshots, where this worked with @Language("sql")
in Giraffe, but has red squigglies in Meerkat FD Canary 7). Samples of the syntax our library's clients will call
Description
Component used: androidx.benchmark.macro Version used: Version 1.4.0-alpha04
Calling
PerfettoTraceProcessor.Session#query
withSELECT slice.name, ...
shows the following error in the IDE:id, name or spec expected, got 'SELECT s...'