Fusion Table API bug, not able to handle WHERE clauses with equality on numeric fields?
===

I'm getting strange results from the FusionTable API. Specifically, it seems unable to handle a simple select statement with equality constraints on numeric values.  Any query I try of the following form:

[SELECT COUNT() FROM 1Nynh5pPrj1q8JqbalppAm-qzAsgKvL0ZRala7VI WHERE AGE=41][1]

yields zero records:

    {
     "kind": "fusiontables#sqlresponse",
     "columns": [
      "count()"
     ],
     "rows": [
      [ "0" ]
     ]
    }

By contrast, a range constraint works fine:

[SELECT COUNT() FROM 1Nynh5pPrj1q8JqbalppAm-qzAsgKvL0ZRala7VI WHERE AGE>40.99 AND AGE<41.01][2]

    {
     "kind": "fusiontables#sqlresponse",
     "columns": [
      "count()"
     ],
     "rows": [
      [  "362" ]
     ]
    }

Maybe the numbers underneath aren't integers?  [SELECT AGE FROM 1Nynh5pPrj1q8JqbalppAm-qzAsgKvL0ZRala7VI WHERE AGE>40.99 AND AGE<41.01][3] return

    {
     "kind": "fusiontables#sqlresponse",
     "columns": [
      "AGE"
     ],
     "rows": [
      [ "41" ],
      [ "41" ],
      [ "41" ],
      ...359 more...
    ]}

Now, maybe there's some floating point representation error going on?  I thought that small integers can be represented exactly as floats (even if some decimal fractions, e.g. 0.1, are repeating decimals in binary).  

It seems unlikely that a bug in Fusion Table SQL would get by without being discovered by others, so perhaps it's there's something unique to how [this particular FusionTable][4] is loaded?


  [1]: https://www.googleapis.com/fusiontables/v1/query?sql=SELECT+COUNT()+FROM+1Nynh5pPrj1q8JqbalppAm-qzAsgKvL0ZRala7VI+WHERE+AGE%3D41&key=AIzaSyBT_ZCriV-Tm78KsJiQp6KKhjDwMhP0tYM
  [2]: https://www.googleapis.com/fusiontables/v1/query?sql=SELECT+COUNT()+FROM+1Nynh5pPrj1q8JqbalppAm-qzAsgKvL0ZRala7VI+WHERE+AGE+%3E40.99+AND+AGE%3C41.01&key=AIzaSyBT_ZCriV-Tm78KsJiQp6KKhjDwMhP0tYM
  [3]: https://www.googleapis.com/fusiontables/v1/query?sql=SELECT+AGE+FROM+1Nynh5pPrj1q8JqbalppAm-qzAsgKvL0ZRala7VI+WHERE+AGE%3E40.99+AND+AGE%3C41.01&key=AIzaSyBT_ZCriV-Tm78KsJiQp6KKhjDwMhP0tYM
  [4]: https://www.google.com/fusiontables/DataSource?docid=1Nynh5pPrj1q8JqbalppAm-qzAsgKvL0ZRala7VI