Trait Source 

pub trait Source {
    // Required methods
    fn open(
        &mut self,
        connection: &Map<String, Value>,
        read_only: bool,
    ) -> Result<()>;
    fn execute(
        &mut self,
        sql: &str,
        row_limit: Option<u64>,
        out: &mut dyn ResultSink,
    ) -> Result<()>;

    // Provided methods
    fn connection_fields(&self) -> Vec<ConnectionField> { ... }
    fn identifier_quote(&self) -> Option<&'static str> { ... }
    fn validate_connection(
        &self,
        _connection: &Map<String, Value>,
    ) -> Vec<String> { ... }
    fn check(&mut self, _sql: &str) -> Result<()> { ... }
    fn load(&mut self, _name: &str, _data: &mut ResultSet<'_>) -> Result<Loaded> { ... }
    fn close(&mut self) { ... }
}

Required Methods

fn open( &mut self, connection: &Map<String, Value>, read_only: bool, ) -> Result<()>

fn execute( &mut self, sql: &str, row_limit: Option<u64>, out: &mut dyn ResultSink, ) -> Result<()>

Run one statement. row_limit is a hint; the SDK enforces it either way.

Provided Methods

fn connection_fields(&self) -> Vec<ConnectionField>

fn identifier_quote(&self) -> Option<&'static str>

The character the database quotes identifiers with, reported in describe: " for most SQL databases, a backtick for Databricks and MySQL. Core doubles it inside a name.

fn validate_connection(&self, _connection: &Map<String, Value>) -> Vec<String>

Rules the declared Source::connection_fields can’t express (two keys that can’t go together, a value’s form), each a sentence naming the field, never its value. Static: no network. Run by validate_connection and before open. A value set through an unset env_var() arrives as null.

fn check(&mut self, _sql: &str) -> Result<()>

Verify without executing. Only called when the plugin advertises check.

fn load(&mut self, _name: &str, _data: &mut ResultSet<'_>) -> Result<Loaded>

Load data into a temporary table on the session, named after name. Only called when the plugin advertises load.

fn close(&mut self)

End the session cleanly (called on close and at end of input, before exiting).

Dyn Compatibility

This trait is dyn compatible.

In older versions of Rust, dyn compatibility was called "object safety".

Implementors