Re: Inconsistent types in PostgreSQL RangeFields

The documentation says, "All of the range fields translate to psycopg2 Range objects in python, but also accept tuples as input if no bounds information is necessary." It looks to me like you could initialize the objects using psycopg's Ra

Inconsistent types in PostgreSQL RangeFields

Hello all, I've been hitting a small annoyance when using the RangeField classes in the PostgreSQL contrib modules : while the value returned by psycopg is a psycopg.extras.Range type, the Django documentation explicitly mentions using tuples when creating and updating model instances. This me