The idea is to come up with a new Transformer and a new Logicsheet that share a common codebase. It will give us
- easier maintenance
- a unified syntax
TODO:
1.identification of the special features of the ESQL logicsheet and the SQLTransformer
1.extension of the feature list (wishlist)
1.coming up with a syntax that supports all this
1.finding a concrete design
1.creation of stylesheets and a script/ant-task for easy migration
1.testing / testcases
1.deprecation of ESQL and the SQLTransformer
The Features
ESQL
- resultset limiting (skip-rows, max-rows)
- Groups are useful for reporting – LauriPitkanen
SQLTransformer
Other
- Pagination – Similar to resultset limiting, but ask the user for page size and page number rather than skip-rows, max-rows. Even though this is easy to calculate, without it the user would have to compute it somewhere else. SteveKrulewitz
- Some way to make sql statements reusable. I'm currently doing this by creating a custom logicsheet that uses ESQL tag. SteveKrulewitz
- Allow the user to put an @id on each query, and write basic information about each query's result into a request attribute, such as number of rows returned. This will allow the pipeline to branch on the result, for example, test if {request-attr:sqlng.theid.numrows} = 0, then go to a no results found page.