Struct diesel::query_builder::BoxedLimitOffsetClause

pub struct BoxedLimitOffsetClause<'a, DB> {
    pub limit: Option<Box<dyn QueryFragment<DB> + Send + 'a>>,
    pub offset: Option<Box<dyn QueryFragment<DB> + Send + 'a>>,
}

A boxed variant of LimitOffsetClause

This type is only relevant for implementing custom backends

Fields

limit: Option<Box<dyn QueryFragment<DB> + Send + 'a>>

The limit clause

offset: Option<Box<dyn QueryFragment<DB> + Send + 'a>>

The offset clause

Trait Implementations

impl<'a> QueryFragment<Pg> for BoxedLimitOffsetClause<'a, Pg>

fn walk_ast<'b>(&'b self, out: AstPass<'_, 'b, Pg>) -> QueryResult<()>

Walk over this QueryFragment for all passes.

fn to_sql(&self, out: &mut DB::QueryBuilder, backend: &DB) -> QueryResult<()>

Converts this QueryFragment to its SQL representation.

fn collect_binds<'b>( &'b self, out: &mut <DB as HasBindCollector<'b>>::BindCollector, metadata_lookup: &mut DB::MetadataLookup, backend: &'b DB, ) -> QueryResult<()>

Serializes all bind parameters in this query.

fn is_safe_to_cache_prepared(&self, backend: &DB) -> QueryResult<bool>

Is this query safe to store in the prepared statement cache?

fn is_noop(&self, backend: &DB) -> QueryResult<bool>

Does walking this AST have any effect?