That’s too bad on both fronts. The persistent state modeling pattern works very well for the TMF RESTful APIs that I’m working to implement using the E2E Builder.
Being able to dynamically build queries for the PersistentStateAdapter would be make handling types like date much easier. It seems it would be pretty straightforward to build the query as a string using ActionScript and then to pass that query string into the PersistentStateAdapter.
Reverting to using a relational database to manage the tickets would make it easier to filter attributes but would lose the state machine features of the persistent state modeling pattern.
Both of these requirements are typical of a RESTful API pattern, sure would be nice if they were supported by the persistent state adapter.