Reviewing it before v. 4.9.3 release: our built-in expression parser is not SQL based and for the time being doesn't support functions. Therefore complex expressions should be calculated as new table fields. I updated docs for Table class to reflect the matter (online version will be updated when beta is released) . The issue with non ASCII characters still needs testing.
↧
