Mike Bayer fce1d954aa implement PG ranges/multiranges agnostically ...

Ranges now work using a new Range object,
multiranges as lists of Range objects (this is what
asyncpg does.  not sure why psycopg has a "Multirange"
type).

psycopg, psycopg2, and asyncpg are currently supported.
It's not clear how to make ranges work with pg8000, likely
needs string conversion; this is straightforward with the
new archicture and can be added later.

Fixes: #8178
Change-Id: Iab8d8382873d5c14199adbe3f09fd0dc17e2b9f1

2022-08-05 10:39:39 -04:00

..

__init__.py

…

test_async_pg_py3k.py

deprecate .connection on _ConnectionFairy, _ConnectionRecord

2022-05-22 15:24:05 -04:00

test_compiler.py

ensure RETURNING renders in stringify w/ no server version

2022-08-03 20:47:27 -04:00

test_dialect.py

implement PG ranges/multiranges agnostically

2022-08-05 10:39:39 -04:00

test_on_conflict.py

Remove object in class definition

2021-11-22 15:03:17 +00:00

test_query.py

use plainto_tsquery for PG match

2022-05-22 15:25:58 -04:00

test_reflection.py

Reflect expression-based indexes on PostgreSQL

2022-07-28 19:27:23 +02:00

test_types.py

implement PG ranges/multiranges agnostically

2022-08-05 10:39:39 -04:00