Opened 9 years ago

Closed 4 years ago

#32 closed enhancement (fixed)

Add support for PostgreSQL arrays

Reported by: cito Owned by: darcy
Priority: major Milestone: 5.0
Component: DB API 2 Version: 4.0
Keywords: arrays Cc:

Description (last modified by cito)

PostgreSQL has an Array type which is currently not yet supported by PyGreSQL e.g. by converting it automatically to Python lists.

This was already mentioned on the mailing list(2008-03-21, 2008-09-09).

This could be made configurable with a switch that would be set to off by default in 5.x, and then in 6.x the switch could be flipped.

Change History (4)

comment:1 Changed 4 years ago by cito

  • Description modified (diff)
  • Milestone changed from 5.0 to 5.1

comment:2 Changed 4 years ago by cito

Arrays can after r772 be read into the database with pgdb. They are not yet converted on output though (and this should be made configurable). They are also not yet supported by pg.

comment:3 Changed 4 years ago by cito

  • Keywords arrays added
  • Milestone changed from 5.1 to 5.0

Arrays are now fully supported after r781.

Keeping this open because we still must discuss whether we should make this feature configurable and what the default configuration should be in 5.0.

comment:4 Changed 4 years ago by cito

  • Resolution set to fixed
  • Status changed from new to closed

This has now been made configurable in r804.

Since I did not get any feedback on this question, I have decided to use the major version change to 5.0 as an opportunity to set all the new features to active, including this one. Everything has been made configurable though and the changelog explains how you can restore the old behavior if you need full backward compatibility. The new features are simply too useful to leave them deactivated until 6.0.

Note: See TracTickets for help on using tickets.