+1 from me as well. It looks mostly like a bug fix update:
3.2.2.1 (2009-10-12)
- [security] XSS and SQL injection, thanks to Herman van Rink
3.2.2.0 (2009-09-13)
- bug #2825293 [structure] Default value for a BIT column
- bug [display] Red arrows were reversed in the list of tables
- bug #2813879 [export] Duplicate empty lines when exporting without comments
- bug #2825919 [export] Trigger export with database name
- bug #2823996 [data] Cannot edit row with no PK and a BIT field
- bug [export] Exporting results of a query which contains a LIMIT clause
inside a subquery
- bug #2837722 [export] Run complex SQL then export does not work
- bug #2839548 [export] Triggers order on export
- bug #2826986 [display] Order by BLOB and range display
- bug [display] After clicking on Show Function or Function, the UPDATE query
is not shown after execution
- bug [structure] Missing validation for BINARY and VARBINARY
+1 from me as well. It looks mostly like a bug fix update:
3.2.2.1 (2009-10-12)
- [security] XSS and SQL injection, thanks to Herman van Rink
3.2.2.0 (2009-09-13)
- bug #2825293 [structure] Default value for a BIT column
- bug [display] Red arrows were reversed in the list of tables
- bug #2813879 [export] Duplicate empty lines when exporting without comments
- bug #2825919 [export] Trigger export with database name
- bug #2823996 [data] Cannot edit row with no PK and a BIT field
- bug [export] Exporting results of a query which contains a LIMIT clause
inside a subquery
- bug #2837722 [export] Run complex SQL then export does not work
- bug #2839548 [export] Triggers order on export
- bug #2826986 [display] Order by BLOB and range display
- bug [display] After clicking on Show Function or Function, the UPDATE query
is not shown after execution
- bug [structure] Missing validation for BINARY and VARBINARY
I'll also ACK the sync.