fmguerreiro opened a new pull request, #2315:
URL: https://github.com/apache/datafusion-sqlparser-rs/pull/2315

   ## Summary
   
   Adds PostgreSQL grammar for the four \`CREATE TEXT SEARCH\` statement 
variants:
   
   - \`CREATE TEXT SEARCH CONFIGURATION name (PARSER = parser_name)\`
   - \`CREATE TEXT SEARCH DICTIONARY name (TEMPLATE = template_name, ...)\`
   - \`CREATE TEXT SEARCH PARSER name (START = fn, GETTOKEN = fn, END = fn, 
LEXTYPES = fn[, HEADLINE = fn])\`
   - \`CREATE TEXT SEARCH TEMPLATE name (LEXIZE = fn[, INIT = fn])\`
   
   Reference: 
https://www.postgresql.org/docs/current/textsearch-dictionaries.html
   
   ## Changes
   
   - Adds four new struct types in \`src/ast/ddl.rs\` 
(\`CreateTextSearchConfiguration\`, \`CreateTextSearchDictionary\`, 
\`CreateTextSearchParser\`, \`CreateTextSearchTemplate\`), each with 
\`fmt::Display\` + \`From<T> for Statement\`.
   - Adds four new \`Statement\` variants and re-exports.
   - Adds \`Spanned\` arms (\`Span::empty()\` stubs — happy to extend with real 
spans if reviewers prefer).
   - Adds a \`parse_create_text_search\` dispatcher in \`src/parser/mod.rs\`.
   - Four round-trip tests in \`tests/sqlparser_postgres.rs\` covering the four 
variants plus optional-clause combinations.
   
   ## Out of scope
   
   \`ALTER TEXT SEARCH\` variants are not included here; scope kept small for 
reviewability.
   
   ## Notes
   
   Originally developed and shipped via the \`pgmold-sqlparser\` fork used by 
[pgmold](https://github.com/fmguerreiro/pgmold); the implementation has been in 
production against real PostgreSQL 13–17 schemas.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to