Make query processor more friendly for embedded usage

[HouzuoGuo]

Currently, the query processor assumes input to be coming from deserialized JSON, therefore some query options such as limit and int-from are expected to be of type float64, which is awkward in embedded usage scenarios.

Change the behaviour so that during query processing, int, int64, uint64 are acceptable when JSON integer is expected.

[jameycribbs]

If you could also include an example in example.go of doing an embedded query without json that would be awesome. I am trying to figure out how to do an intersection query without first having to marshal to and then unmarshal from json. I am very new to go, so I know that is a big part of the problem, but if there was an example of what an intersection query looked like using native go structures, rather than json, it would be greatly appreciated.

[HouzuoGuo]

thanks very much & will do

[archey]

@HouzuoGuo maybe this one can be solved now as well? So it can be fixed for good

[HouzuoGuo]

@archey Good idea, but at the moment I'm working on some features in https://github.com/HouzuoGuo/websh. Are you feeling adventurous to add those examples to example.go?