psycopg/psycopg2
1
1
Fork 0
mirror of https://github.com/psycopg/psycopg2.git synced 2025-10-31 15:57:31 +03:00
Code Issues Packages Projects Releases Wiki Activity

documentation changes now that Range objects can be ordered

Browse Source
This commit is contained in:
Chris Withers 2014-02-18 21:24:59 +00:00 committed by Daniele Varrazzo
parent 1487800b6d
commit 5624ad4ec5
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/src/extras.rst
View File

@ -437,9 +437,14 @@ user-defined |range| types can be adapted using `register_range()`.
`!Range` objects are immutable, hashable, and support the ``in`` operator `!Range` objects are immutable, hashable, and support the ``in`` operator
(checking if an element is within the range). They can be tested for (checking if an element is within the range). They can be tested for
equivalence but not for ordering. Empty ranges evaluate to `!False` in equivalence. Empty ranges evaluate to `!False` in
boolean context, nonempty evaluate to `!True`. boolean context, nonempty evaluate to `!True`.
`!Range` objects can be sorted although, as on the server-side,
this ordering is not particularly meangingful.
.. versionchanged:: 2.5.3
Although it is possible to instantiate `!Range` objects, the class doesn't Although it is possible to instantiate `!Range` objects, the class doesn't
have an adapter registered, so you cannot normally pass these instances as have an adapter registered, so you cannot normally pass these instances as
query arguments. To use range objects as query arguments you can either query arguments. To use range objects as query arguments you can either