Austin Bonander
Austin Bonander
`timestamptz` is a _little_ more complicated than that, because while it may be stored and transmitted in the binary protocol as UTC, in the _text encoding_ it may include a...
Why is the use of `Zoned` an issue? Can it not convert to UTC when encoding? Yes, it loses the timezone information, but it likely would anyways. The big problem...
> So you're an hour off because your arithmetic didn't take DST into account. And that happened because your `Zoned` value got silently and lossily transmitted into PostgreSQL. Well, to...
> > The sqlx chrono integration here might be buggy. See: > > Yeah. I report it at [#703 (comment)](https://github.com/launchbadge/sqlx/issues/703#issuecomment-2359949473) but it seems missed. A PR is always welcome.
@BurntSushi the biggest difference between Postgres and MySQL/SQLite is the types supported by the former is an open set (it supports user and extension-definable types) while both of the latter...
As for SQLite, [these types are all pseudo-types](https://github.com/launchbadge/sqlx/blob/3a20a92a3fd90b84d5fd5fa3ebddc7f190e9ae1b/sqlx-sqlite/src/type_info.rs#L30-L37) only used within the SQLx API. The date/time related types here are purely to return something more specific than `"TEXT"` if you...
> The minimal example above should reproduce the error. @zbrox that is not a sufficiently minimal example. There's no table schema, nor a definition for `SearchResult`. It should not require...
I appreciate the effort on this, but in #3364 kind of got stuck on some design questions. I was thinking that I would: * Delete the `Execute` trait because it...
Yeah, deleting the lifetimes on `Arguments` was an idea, though `AnyArguments` also uses it when encoding `&str` and `&[u8]`. It saves a copy when later encoding into the database-specific format.
CI should be fixed if you rebase.