Stefan E

I am facing the same problem, but with base plot as well. Did anyone find a solution? Otherwise there should possibly be a feature request.

This is affecting us as well via the react-native port. Migrating to the new v10 is unfortunately not an option.

> The suggested workaround does not seem to work and produces several warnings: > > `Warning` messages: 1: In if (!is.na(ns_glyph_attrs[[ii]]$value)) ns_glyph_attrs[[ii]]$value 1 and only the first element will be...

> More and more users are using the official Mapbox SDK through react-native-mapbox-gl Some [usage statistics](https://npm-stat.com/charts.html?package=%40react-native-mapbox-gl%2Fmaps&from=2019-02-02&to=2021-10-31) to quantify this:  When `@mapbox/react-native-mapbox-gl` was deprecated, it had roughly 16k downloads...

This is helpful: https://stackoverflow.com/questions/69538962/new-nativeeventemitter-was-called-with-a-non-null-argument-without-the-requir A pull request like this might fix this: https://github.com/microsoft/appcenter-sdk-react-native/pull/942/files

Thanks for your valuable time! I created a minimal working example that should demonstrate my case. Parallel inserts don't work anyways due to #33 I suppose, but even without parallel...

Cheers. There is no error message. With ```python cursor.insert('points', {"Z": np.random.rand(10000000)}) ``` the behaviour does not change.

Hi, sounds like you figured out and tested a solution already! Would you commit this change yourself?

Hi, I don't have permissions to merge this in anymore. Maybe @masain does?

Just another use case here: We would like to do 2D points-in-polygon-filtering on a point cloud (xyz data) with 4B points. Performance decreases roughly linearly with table size. With 700k...