Struct pgx::prelude::Interval

#[repr(transparent)]
pub struct Interval(_);

From the PG docs https://www.postgresql.org/docs/current/datatype-datetime.html#DATATYPE-INTERVAL-INPUT Internally interval values are stored as months, days, and microseconds. This is done because the number of days in a month varies, and a day can have 23 or 25hours if a daylight savings time adjustment is involved. The months and days fields are integers while the microseconds field can store fractional seconds. Because intervals are usually created from constant strings or timestamp subtraction, this storage method works well in most cases…

Implementations

impl Interval

pub fn try_from_months_days_micros( months: i32, days: i32, micros: i64 ) -> Result<Self, IntervalConversionError>

This function takes months/days/microseconds as input to convert directly to the internal PG storage struct pg_sys::Interval

• the sign of all units must be all matching in the positive or all matching in the negative direction

pub fn from_ptr(ptr: NonNull<Interval>) -> Self

pub fn as_ptr(&self) -> NonNull<Interval>

pub fn months(&self) -> i32

Total number of months before/after 2000-01-01

pub fn days(&self) -> i32

Total number of days before/after the months() offset (sign must match months)

pub fn micros(&self) -> i64

Total number of microseconds before/after the days() offset (sign must match months/days)

Trait Implementations

impl Debug for Interval

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl FromDatum for Interval

unsafe fn from_polymorphic_datum( datum: Datum, is_null: bool, _typoid: Oid ) -> Option<Self>where Self: Sized,

Like from_datum for instantiating polymorphic types which require preserving the dynamic type metadata.

const GET_TYPOID: bool = false

Should a type OID be fetched when calling from_datum?

unsafe fn from_datum(datum: Datum, is_null: bool) -> Option<Self>where Self: Sized,

Safety

unsafe fn from_datum_in_memory_context( memory_context: PgMemoryContexts, datum: Datum, is_null: bool, typoid: Oid ) -> Option<Self>where Self: Sized,

Default implementation switched to the specified memory context and then simply calls FromDatum::from_datum(...) from within that context.

unsafe fn try_from_datum( datum: Datum, is_null: bool, type_oid: Oid ) -> Result<Option<Self>, TryFromDatumError>where Self: Sized + IntoDatum,

try_from_datum is a convenience wrapper around FromDatum::from_datum that returns a a Result around an Option, as a Datum can be null. It’s intended to be used in situations where the caller needs to know whether the type conversion succeeded or failed.

unsafe fn try_from_datum_in_memory_context( memory_context: PgMemoryContexts, datum: Datum, is_null: bool, type_oid: Oid ) -> Result<Option<Self>, TryFromDatumError>where Self: Sized + IntoDatum,

A version of try_from_datum that switches to the given context to convert from Datum

impl IntoDatum for Interval

fn into_datum(self) -> Option<Datum>

fn type_oid() -> Oid

fn composite_type_oid(&self) -> Option<Oid>

fn array_type_oid() -> Oid

fn is_compatible_with(other: Oid) -> bool

Is a Datum of this type compatible with another Postgres type?

impl Serialize for Interval

fn serialize<S>(&self, serializer: S) -> Result<S::Ok, S::Error>where S: Serializer,

Serialize this value into the given Serde serializer.

impl SqlTranslatable for Interval

fn argument_sql() -> Result<SqlMapping, ArgumentError>

fn return_sql() -> Result<Returns, ReturnsError>

fn type_name() -> &'static str

fn variadic() -> bool

fn optional() -> bool

fn entity() -> FunctionMetadataTypeEntity