Fix: Final refinement of plugin compatibility regexes for multi-line and trailing LIMIT

Author: wp-fuse

integrations/plugin-compatibility/boot.php

@@ -28,11 +28,11 @@ function wp_sqlite_integration_plugin_compat( $query ) {
 		return 'SELECT 1 WHERE 1=0';
 	}
 
-	// 2. Global fallback for FOR UPDATE / SKIP LOCKED.
+	// 2. Global fallback for FOR UPDATE / SKIP LOCKED / NOWAIT.
 	// This ensures the legacy driver natively ignores these locking constraints where SQLite faults.
-	// We use a non-destructive lookahead for whitespace, semicolon, or comments to avoid destroying strings.
+	// We use a non-destructive lookahead for whitespace, semicolon, comments, or LIMIT.
 	if ( stripos( $query, 'FOR UPDATE' ) !== false ) {
-		$query = preg_replace( '/\s+FOR\s+UPDATE(?:\s+(?:SKIP\s+LOCKED|NOWAIT))?(?=\s*(?:;|\/\*|$))/i', '', $query );
+		$query = preg_replace( '/\s+FOR\s+UPDATE(?:\s+(?:SKIP\s+LOCKED|NOWAIT))?(?=\s*(?:;|\/\*|$|\s+LIMIT))/is', '', $query );
 	}
 
 	// 3. Action Scheduler specific compatibility fixes.