QuestDB support #2
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SuficioAC
force-pushed
the
union-nullable
branch
from
97194b6 to
79ae3e5
Compare
* impl AnyQueryResult for Sqlite and MySQL * fix MySQL AnyQueryResult * fix MySQL AnyQueryResult * fix manifest * rewrite `use` and address implementation concerns
Alternative option for the sqlx::test fixtures referenced the same fixture twice
* feat: point * test: try if eq operator works for arrays of geometries * fix: re-introduce comparison * fix: test other geometry comparison * test: geometry array equality check * test: array match for geo arrays geo match for geo only * fix: prepare geometric array type * fix: update array comparison * fix: try another method of geometric array comparison * fix: one more geometry match tests * fix: correct query syntax * test: geometry test further
query_as.rs: 230 mismatched bracket. query_as.rs: 230 move TIMESTAMP to TIMESTAMPTZ to match type time::OffsetDateTime. query_as.rs: 241, 251, 260 move i64 to i32 to match postgres type `INT4`.
When PgListener's underlying connection is closed, try_recv() will return Ok(None) and reconnect on the next call. In this case, user code is supposed to reload its state from the database (or otherwise handle potentially missing messages). However, if the user code uses another database connection to do so then there is a period between when the state is reloaded and PgListener's connection is re-established where notifications are lost without any indication that this has happened. This commit changes PgListener to eagerly reconnect by default. At the suggestion of @abonander on discord, I have also included an option to switch back to the old behaviour in the case where someone was depending on it. Now, if the connection is closed then, by default, user code can do whatever it needs to do in order to recover and any notifications emitted in the meantime will be waiting for it when it is done.
…ications (launchbadge#3560) * Implement and test PgListener::try_recv_buffered(). * rustfmt * Fix warnings. * Fix test. * Rename try_recv_buffered() -> next_buffered().
* feat(mysql): support configuring the timezone via url * test: add test case for mysql with timezone --------- Co-authored-by: lo <[email protected]>
Duplicates the fix to Postgres in launchbadge#3593 to the MySQL driver. The SQLite driver already does this: https://github.com/launchbadge/sqlx/blob/e3ef8baf23bc0266959282814c014e482418eef2/sqlx-sqlite/src/options/parse.rs#L29-L32
For database-specific types.
This adds an alternative TLS configuration that relies on rustls-native-certs, for users who cannot bundle the MPL-licensed webpki-roots. The approach is copied from reqwest: * https://github.com/seanmonstar/reqwest/blob/3ad6e02cd/Cargo.toml#L48 * https://github.com/seanmonstar/reqwest/blob/3ad6e02cd/src/async_impl/client.rs#L513 — except error handling is relaxed to accommodate for tls_config.root_cert_path.
An lquery array can be used with the `?` operator for "Does ltree match any lquery in array?" Documentation: https://www.postgresql.org/docs/current/ltree.html#LTREE-OPS-FUNCS Closes launchbadge#2246
* chore: reduce BoxFuture's when using recursion. * remove BoxFuture's in WithSocket * chore: better document previous changes
* feat: add geometry line * fix: point vs line * fix: try regular comparison for line * fix: undo point comparison change * fix: regular comparison for array lines * fix: remove line array test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Does your PR solve an issue?
Delete this text and add "fixes #(issue number)"