Elliana May

DuckDB doesn't really have a concept of cursors at all, hence why the `CursorWrapper`, etc, exist in the `duckdb_engine` codebase. If you want to be able to have multiple queries...

While we're fixing this, might be worth extending the docstring to include docs for the individual parameters using the Sphinx/RST syntax so it appears in the auto-generated docs

I think it would probably be worth waiting for https://github.com/beeware/toga/pull/2999 to be merged before looking to merge this

> Noted about waiting until #2999 lands; but this looks pretty solid. > > My only big question stems from the what the watcher API is being used. AIUI, this...

I guess another alternative to improve the location quality, would be to await a decent quality location being returned (by tweaking the config on the watcher itself maybe)

> > That does somewhat make sense yes, aside from the fact that `onPermissionStatusChanged` doesn't actually exist 😉 > > I can see how that could be a possible impediment...

Actually, looks like we can use https://learn.microsoft.com/en-us/dotnet/api/system.device.location.geocoordinatewatcher.onpropertychanged?view=netframework-4.8.1#system-device-location-geocoordinatewatcher-onpropertychanged(system-string) to monitor the permission states

I can't say I'd really recommend this, but you can do this to work around that error: ```py from duckdb_engine import ConnectionWrapper engine = sa.create_engine("duckdb://", creator=lambda: ConnectionWrapper(con)) ``` this class...

Sounds like this is a Gradle specific issue then?

It's possible the underlying issue is https://github.com/gradle/gradle/issues/15095