Latest Contributions by JoshuaBixby

Is there a reason you are looking at 9.3 Help even though you are using 10.2?  A lot has changed in nearly 7 years. ... View more

You might want to try: field = "COUNTY_CODE" where_clause = "{} = '{}'".format(field, code[0]) or where_clause = "COUNTY_CODE = '{}'".format(code[0]) You don't need to put your field name in quotes, but the value itself will need to be in quotes if it is text. I strongly encourage you to read up on Python String Formatting.  It is much more powerful and Pythonic for building SQL expressions than concatenating strings together. ... View more

Not completely sure this will address your need, although I think it is in the ballpark: Geodatabase Geek - THE “INVERSE” MULTI-VERSION VIEW Although I am not currently implementing it, I did implement it on a project years back.  If my memory serves me, it worked well, and I especially liked that it was a SQL view so you can check for all of the edits at any time you want by refreshing the view. ... View more

It is helpful to review the Help for Building a query expression, where it states: If the string contains a single quote you will first need to use another single quote as an escape character. In Python, the backslash is the dominant escape character, but there are some additional escape sequences. ArcGIS wants users to escape a single quote by using another single quote. I see that Xander Bakker‌ beat me to the punch with the actual code.  That's what getting distracted while replying gets me. : ) ... View more

The tool won't "see" the SQLite database for the same reason the Project pane doesn't; however, the tool works with them.  Don't rely on the tools Browse button, fully specify the path to the table in the SQLite database in the Input Features text box. ... View more

Are you trying to load spatial data or just a table?  Was the SQLite database created by ArcGIS Desktop or some other application?  If the latter, try making a SQLite database from ArcGIS Desktop and putting some data in it, and then see if ArcGIS Pro sees that database, especially if working with spatial data. ... View more

If communicating with Esri feels like screaming in the wind at times, dealing with Apple is like having that conversation in an asylum.  I gave up on them a long time ago, which is too bad because they do make some good products. ... View more

It is easier for fellow GeoNet community members to provide feedback if you post relevant, functional parts of your code. ... View more

I think Esri would agree, i.e., SQLite isn't currently fully supported in ArcGIS Pro. Although "seeing" SQLite databases isn't possible through the Project pane/window, you can load SQLite databases using the Make Feature Layer tool either through the GUI or ArcPy.  At least during beta testing, Spatialite-based spatial data wouldn't load because the correct DLLs weren't packaged with the installer, not sure if that changed.  I have successfully loading ST_Geometry and GeoPackage spatial data into ArcGIS Pro. ... View more

You can force indexes through Query Hints (Transact - SQL).  That said, forcing an index may not improve performance, sometimes it makes performance worse.  Since it seems you are in a development/testing phase and not writing production code yet, it might not hurt to experiment with forcing the different indexes to see what happens.  If forcing an index does help, especially dramatically, then the question becomes why isn't the query optimizer choosing to use either index.  By the way, I believe it is still true that SQL Server can only use one spatial index in a single query, but that may have changed. If you haven't already, you may want to review SQL Server 2012 - Spatial Indexes Overview.  The more you understand how MS has implemented spatial indexes, the less of a black box it will all seem, which makes for better SQL troubleshooting.  Also, there are some very specific syntax rules for maximizing a nearest neighbor type of query, which you are trying to do in some form. Beyond reading MS's overview, there are some good blogs and MSDN discussions on tuning SQL Server spatial indexes. Taking a quick glance at your specific code, you are missing some of the requirements for a spatial index to be used.  As the overview documentation I linked to above states: Geometry Methods Supported by Spatial Indexes Spatial indexes support the following set-oriented geometry methods under certain conditions: STContains(), STDistance(), STEquals(), STIntersects(), STOverlaps(), STTouches(), and STWithin(). To be supported by a spatial index, these methods must be used within the WHERE or JOIN ON clause of a query, and they must occur within a predicate of the following general form: .... ... View more

That error with findAndReplaceWorkspacePath is common when you are trying to not just replace the workspace path but also the workspace type.  Are you switching from a personal geodatabases to a file geodatabases?  If you are switching workspace types as well, then you need to use replaceDataSource as Xander Bakker‌ suggests. Also, if you are going to be coming across group layers or layers with lots of different data sources, it is good to use the layer.supports method to check the layer supports a data source property. ... View more

You mention "query table."  Are you using Make Query Table or Make Query Layer?  Make Query Table is powerful, but it is an older tool, and I am not sure if its outputs are editable. I just did a quick test using Make Query Table where I took a single feature class and used Make Query Table to create a layer, so this is a very simple case without multiple data sets or joins.  Although I could use an update cursor on the feature class directly, I could not use it on the layer created from Make Query Table. ... View more

Although using lists for field names is much more common, tuples are supported.  I am leaning more towards the query table. ... View more