Opened 14 years ago

Last modified 14 years ago

#2068 new bug

PostGIS attribute table annoyance

Reported by: imincik1 Owned by: nobody
Priority: minor: annoyance Milestone: Version 1.7.0
Component: Digitising Version: Trunk
Keywords: Cc:
Must Fix for Release: No Platform: All
Platform Version: Awaiting user input: no

Description

After editing and saving PostGIS attribute data using 'attribute table', edited record is moving at the and of attribute table with no respect to column sort order. Sometimes also during editing records are resorting in unpleasant order. This behavior makes user confusing, he/she can think that edited data has disappeared.

Try:

  1. Open 'attribute table' of some PostGIS layer in editing mode.
  2. Sort rows by column 'gid'.
  3. Edit some attribute value (not gid), for example row with gid 5. Sometimes also at this point, records are reordered.
  4. Save table. At this point, all changed rows are usually moved at the bottom of attribute table, no matter if I sort table by gid (which is not changed).

Note: It seams that this behavior is getting worse when table is edited and saved multiple times.

Change History (3)

comment:1 by pcav, 14 years ago

Summary: PostGIS attribute table annoymancePostGIS attribute table annoyance

comment:2 by pcav, 14 years ago

Milestone: Version 1.6.0

Still true? Please chack with a newer version and close this if appropriate

comment:3 by imincik1, 14 years ago

Yes, it is still there. Test was made on latest trunk using Debian Lenny.

  1. Import new polygon layer to PostGIS using SPIT plugin
  2. Open attribute table and start to edit. By default records are ordered by 'gid'. Edit some attribute value and save. After doing this multiple times, edited value will disappear on save (sometime it will be on the bottom of attribute table, sometimes nowhere). I will appear after manual reordering of table on 'gid' column.

Sometimes, when it was harder to reproduce this behavior, ordering by some other attribute column than 'gid', editing, saving, ordering by 'gid' again, editing and saving helped me to reproduce.

Note: See TracTickets for help on using tickets.