…ithout attributes - corresponding to the: select itemName() from <domain> where <expression> syntax.
The select attribute syntax documentation reads: "An explicit list of attributes (attribute1,..., attributeN)" However, the parenthesis are used only for punctuation within the documentation, and the actual select statement should be sent unadorned: select attribute1, attribute2 from ... Signed-off-by: Robin Barooah <firstname.lastname@example.org>
…'t get applied. As a result I'm changing them to is and is_not. This is probably a better idea anyway since otherwise they could be confused with the scala operators.
…the same syntax as it used to do with the 'Query' DSL
…fferent forms of select using partial functions.
When mapping from attribute names to attribute positions for the GetAttributes/QueryWithAttributes requests, the position was not incremented, and only the final attribute was included in the request, as the position 0 attribute. Signed-off-by: Robin Barooah <email@example.com>
… but since we just changed the underlying format in an incompatible way, it's actually better this way.
…pecifier rather than an offset that might make it look as though other offsets are supported.
To provide safe lexicographical comparison of dates, they must use a consistent time zone. This change updates the timezone to UTC. Additionally, the SimpleDateFormatter is documented as being non-threadsafe and requiring synchronization. This patch also adds per-request instantiation of the date formatter to avoid these issues. Signed-off-by: Robin Barooah <firstname.lastname@example.org>
The implementation places no upper bound on open connections, as SimpleDB is intended to support high, parallel connection load. Idle connections are arbitrarily constrained to 100, with eviction occuring at 5 minute intervals. Signed-off-by: Robin Barooah <email@example.com>
…en parsing errors.
…er libraries etc. This may look like heresy, but since to get this far you have put them in a text file on the classpath, this is no worse.