GeezerVison

Summary

Fixes #655. CreateStatement::build() reconstructed CREATE VIEW ... AS SELECT ... UNION ... by concatenating $builtStatement = $this->select->build() directly with TokensList::buildFromArray($this->body). Neither side carried a separator, so the rebuilt SQL collided the SELECT's last token with the UNION:

... WHERE 3 = 3union all (...)

This was reported downstream in phpmyadmin/phpmyadmin#19692 (and earlier as #18515), the syntax-invalid output broke phpMyAdmin's exports.

Change

src/Statements/CreateStatement.php, insert a single space when both sides are non-empty and neither already ends/begins with a space. The existing WITH ... AS ( ... ) SELECT ... path already produces a trailing space on $builtStatement, so the conditional avoids double-spacing it.

Test plan

• vendor/bin/phpunit tests/Builder/, 110/110 pass (including the existing testBuilderView which already exercised UNION on a different shape)
• New testBuilderViewWithUnionPreservesWhitespace reproducing the issue's exact CREATE ALGORITHM=UNDEFINED ... AS select 1 AS \`a\` where 3 = 3 union all (...) input. Asserts:
  • rebuilt SQL does not contain 3union all (collision)
  • rebuilt SQL does contain 3 union all (case-normalised)
• Existing WITH+UNION test (CREATE view view_name AS WITH aa(col1) AS (...) SELECT ...) unchanged, the conditional separator preserves its prior trailing-space output