Add Tuple property to provide an immutable variant of List

Bug #582256 reported by Dan Halbert on 2010-05-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

The List property supports PostgreSQL ARRAY[] column types. But because a List is mutable, it has to be checked for changes on every flush(). If many Lists are cached, this can be slow. The alternative is to invalidate() object holding the List to remove it from the cache, but that is a nuisance and you may want it to stay in the cache.

This patch adds a Tuple property for ARRAY[], which is like List but is immutable, so it is does not need to be checked on flush().

The code for Tuple is mostly copied from List with minor changes. Unit tests are included.

For background on this change, see

Jamu Kakar (jkakar) on 2010-05-18
Changed in storm:
assignee: nobody → Dan Halbert (halbert)
milestone: none → 0.17
importance: Undecided → Medium
status: New → In Progress
Dan Halbert (dhalbert) wrote :

Due to some employment-related issues, I have had to withdraw this patch. I may redo it at some point in the future, and I invite someone else to work on this if they wish.

Changed in storm:
status: In Progress → Incomplete
James Henstridge (jamesh) wrote :

Marking as confirmed. While we no longer have an implementation, the feature request is still valid.

Changed in storm:
assignee: Dan Halbert (halbert) → nobody
milestone: 0.17 → none
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers