topic Re: Trouble executing SQL querying string coded values in File Geodatabase API Questions

Trouble executing SQL querying string coded values

MarkCederholm — Tue, 22 Jan 2013 21:18:38 GMT

I'm having trouble querying string coded values via ExecuteSQL in the API. I can query numeric codes just fine, for example:

SELECT * FROM street_anno WHERE horizontalalignment = 1

Most of my coded value domains are strings where the code and the name are the same. If I query against a particular code, no rows are returned:

SELECT * FROM station WHERE feature_status = 'As-Built';

I only get rows returned if I query against the first character of the code:

SELECT * FROM station WHERE feature_status LIKE 'A%';

Any ideas? Perhaps it's a unicode issue? I'm using 1.3 BTW.

Re: Trouble executing SQL querying string coded values

MarkCederholm — Wed, 23 Jan 2013 12:53:26 GMT

Well, DUH, it would help if I didn't convert the value I was looking for to upper case! I didn't even notice that yesterday. 😛

One thing I DID notice, however: whether I use ExecuteSQL or Table.Search, output is not confined to specified subfields. A row is fully populated in any case.

Re: Trouble executing SQL querying string coded values

DavidSousa — Thu, 30 May 2013 22:27:37 GMT

Unfortunately, you cannot use your coded value domains in a SQL statement or WHERE clause. This is true in ArcGIS as well.

You are correct that at the present time, the fields in the row set of a query are not restricted to the fields specified in the select list. That is something that will be corrected in a future release, but in the meantime, it is not harmful.