Propel Criteria Builder

Criteria demo

This is an alpha-release of a utility that converts pseudo-SQL into PHP Propel code. Give it a try — feedback is welcome on the symfony forum!

Enter pseudo-sql

Columns must be in the form table.field and strings must be in single quotes. Supported comparison operators are =, <>, !=, <, >, <= and >=. Also allowed are LIKE, NOT LIKE, IN, NOT IN, IS NULL and IS NOT NULL. In strings, the apostrophe character can be escaped with the use of a backslash. Brackets to any depth are fine, and clauses can be joined with AND and OR. No subclause may contain both AND and OR - use brackets to indicate precedence.

To-do list

~~Unit tests for parser~~

~~Round brackets within quoted strings causes parse error~~

~~Accidental token markers in strings are dealt with incorrectly~~

~~Ensure semi-quoted strings in IN clauses throw an error~~

~~Convert table to peer name correctly (map_zone is parsed Map_zonePeer instead of MapZonePeer) - thanks Piwaï~~

Support Propel 1.3 PropelPDO clauses

~~Support comparisons with negative numbers - thanks Piwaï~~

Subclause parses incorrectly when joined by something other than AND or OR

~~Support IS NULL and IS NOT NULL~~

Use $c->addAnd() or $c->addOr() rather than Criterions for boolean expressions at the first level of the expression hierarchy

~~Allow backslash to act as escape character in quoted strings~~

~~IN and NOT IN arrays should be allowed to contain one element~~

~~Correctly interpret NOT LIKE and NOT IN if they contain more than one space character~~

~~Radio buttons to choose Propel arrays or ResultSet result~~

~~Tickbox to include demo iterative loop~~

~~Remove redundant carriage returns in input~~

Preserve options upon query submit

Collapse multiple ORs on the same field to IN

Allow spec of ASC and DESC sort columns

Improve the grouping of criterion creation and merging - thanks Piwaï

Determine peer class from a FROM clause, or allow it to be entered

Database-sensitive understanding of the wildcards in LIKE?

Allow a limit clause

Option to concatenate Criterion object ops (eg: $crit0->addAnd($crit1)->addAnd($crit3);)

Complain if the same field appears in more than one equality comparison in an AND sub-clause

If a nested op is the same as the op in the clause above, flatten the structure

Suppress comments for AND/OR when processing just a single subclause

Support schema-based joins