Limitations for definition queries?

[CharlieRichman]

I'm currently querying 6,000 or so polygons from a service as part of my app startup, adding them to a "local" featurelayer via a featurecollection, and using them effectively for local data editing and exploration.

Performance on panning would be better, though, if I could render the unedited polygons on the server and only the edited ones locally.  Before I explore that route, though I'd like to understand  the limitations on definition query complexity.  We might have several hundred edits (out of 6,000).  Could I feed a definition query to the server that amounted to "give me everything except these 295 specific features?".  (Past experience makes me suspicious of long definition queries.)

Thanks

Charlie Richman
DC Office of Planning

[BjornSvensson]

Yes you can 🙂

This is similar to how we do the 'onDemand' mode for a FeatureLayer (by not asking for the OBJECTIDs that are already on the client).  If you do it on any other field make sure it's indexed properly.

[CharlieRichman]

That sounds very promising!

Any suggestions for the most effective way to structure that kind of query?

Charlie Richman
DC Office of Planning

[DasaPaddock]

Try: OBJECTID NOT IN (1, 2, 3)