fn check_error(e: Error) -> Result<()> {
    if e.code() == Some(&SqlState::SQL_STATEMENT_NOT_YET_COMPLETE) {
        log::info!("Error querying, will try again... {}", e.to_string());
        Ok(())
    } else {
        Err(anyhow::Error::from(e))
    }
}
/// The SQL_STATEMENT_NOT_YET_COMPLETE error will surface if we query a view in
/// Materialize before data exists for that view. It is common to hit this error
/// just after creating a view, particularly in testing or demo code.
///
/// Since this error is likely transient, we should retry reading from the view
/// instead of failing.
The SQL_STATEMENT_NOT_YET_COMPLETE error will surface if we query a view in
Materialize before data exists for that view. It is common to hit this error
just after creating a view, particularly in testing or demo code.

Since this error is likely transient, we should retry reading from the view
instead of failing.
The SQL_STATEMENT_NOT_YET_COMPLETE error will surface if we query a view in Materialize before data exists for that view . It is common to hit this error just after creating a view particularly in testing or demo code . Since this error is likely transient we should retry reading from the view instead of failing .
fn check_error(e: Error) -> Result<()> {
    if e.code() == Some(&SqlState::SQL_STATEMENT_NOT_YET_COMPLETE) {
        log::info!("Error querying, will try again... {}", e.to_string());
        Ok(())
    } else {
        Err(anyhow::Error::from(e))
    }
}
fn check_error ( e : Error ) -> Result < ( ) > { if e . code ( ) == Some ( & SqlState :: SQL_STATEMENT_NOT_YET_COMPLETE ) { log :: info ! ( " " e to_string ( ) ) ; Ok ( ( ) ) } else { Err ( anyhow :: Error :: from ( e ) ) } }
The SQL_STATEMENT_NOT_YET_COMPLETE error will surface if we query a view in
Materialize before data exists for that view.
The SQL_STATEMENT_NOT_YET_COMPLETE error will surface if we query a view in Materialize before data exists for that view .
e
Error
e
Error