fix: adapt statement regexp to work with create or replace function statements

Author: psteinroe

crates/parser/src/source_file.rs

@@ -12,9 +12,7 @@ use crate::{parser::Parser, syntax_kind::SyntaxKind};
 #[derive(Logos, Debug, PartialEq)]
 #[logos(skip r"[ \t\f]+")] // Ignore this regex pattern between tokens
 pub enum SourceFileToken {
-    // TODO: this only parses based on the semicolon, which will fail for statements that contain
-    // subexperessions such as transactions or functions.
-    #[regex("[a-zA-Z0-9_]+[^;]*;"gm)]
+    #[regex("[a-zA-Z0-9_]+(?:'[^']*'|(?:\\$\\$[^$]*\\$\\$|[^';])+)*;"gm)]
     Statement,
     #[regex("\n+"gm)]
     Newline,

crates/parser/src/statement.rs

@@ -143,6 +143,8 @@ impl Parser {
         // parse root node if no syntax errors
         if pg_query_nodes.peek().is_some() {
             let (node, depth, _) = pg_query_nodes.next().unwrap();
+            // TODO: if root node is a create or alter function stmt, parse the function body
+            // separately
             self.stmt(node.to_enum(), range);
             self.start_node_at(SyntaxKind::from_pg_query_node(&node), Some(depth));
             self.set_checkpoint(false);