Skip to main content

parse_lo_file_call

Function parse_lo_file_call 

Source
pub fn parse_lo_file_call(sql: &str) -> Option<LoFileCall>
Expand description

Recognise a bare SELECT lo_import(…) / SELECT lo_export(…).

Deliberately narrow: only the statement-level spelling is intercepted, which is the one that reaches a file. Anything else — the call nested in a larger expression — is left to the ordinary evaluator, which reports it as unsupported rather than silently doing nothing.