Support more types

[barsdeveloper]

Hello, do you plan to support more types like Float, Time, Date, Decimal, Map etc. Many modern databases support those types. Also the list of supported types seems very narrow I get the impression that it supports sort of minima common denominator, is the design to support DB specific types still in progress or there are no plans?

pub enum Value {
    /// Boolean value
    Bool(bool),

    /// Value of an enumerated type
    Enum(ValueEnum),

    /// Signed 64-bit integer
    I64(i64),

    /// A unique model identifier
    Id(Id),

    /// A typed record
    SparseRecord(SparseRecord),

    /// Null value
    #[default]
    Null,

    /// Record value, either borrowed or owned
    Record(ValueRecord),

    /// A list of values of the same type
    List(Vec<Value>),

    /// String value, either borrowed or owned
    String(String),
}

[carllerche]

Yes, I plan to support many types. Right now, I'm focusing on a SQL serializer refactor. The next step will be adding MySQL support. After that, it will be time to expand the number of supported types. I am following this order because this will help inform the details of adding more types as there will be variance between how each database supports the details of each type.

[Wragdan]

@carllerche Will implementing new types be responsibility of the user or will it be implemented here using features? Is it okay if I send a PR for supporting uuid:Uuid for example?

[carllerche]

Common types will be included with Toasty by default. I think Uuid is common enough to add. However, it raises a question that must be addressed. Does Toasty provide its own Uuid type (as a wrapper around some crate)? Or does toasty re-export a Uuid type? I guess that it should be the first option.

If you want to look at a Uuid type, go for it. I expect that will hit some design decisions that I haven't considered yet, but we can work through them.