Branch | Commit message | Author | Age | |
---|---|---|---|---|
master | Fix the jdbc query executor for insert/update/delete operations | Carlo Zancanaro | 11 years | |
Age | Commit message | Author | ||
2013-11-25 | Fix the jdbc query executor for insert/update/delete operationsHEADmaster | Carlo Zancanaro | ||
2013-11-25 | Remove a stupid testing thing, update the README a touch | Carlo Zancanaro | ||
2013-11-25 | Add a 'distinct' operator - still a bug to fix on renaming | Carlo Zancanaro | ||
2013-11-12 | Fix the database type detection in the jdbc executor | Carlo Zancanaro | ||
2013-11-12 | Potentially misleading typo | Carlo Zancanaro | ||
2013-11-12 | Change the query executor model: now it's query local and the interface is ma... | Carlo Zancanaro | ||
2013-11-12 | Fix a minor error in the README. | Carlo Zancanaro | ||
2013-11-12 | Ah, screw it. Have super long lines in the README. | Carlo Zancanaro | ||
2013-11-12 | Fix up the README which I formatted wrong. Whoops! | Carlo Zancanaro | ||
2013-11-12 | Fix grouping - it used to allow for groupings leaving a non-grouped field...Now it takes a third "projection" argument in which one can perform aggregate function over the existing fields. The fields of the resulting query are the union of the grouping fields and the projected fields (with the projected fields taking precedence). If you try to project a field without applying some sort of function to it then you'll get an exception, but at the moment no function calls are actually validated as aggregate functions (in order to do so we'd need a knowledge of all the aggregate functions, which isn't possible in general). | Carlo Zancanaro | ||
[...] |