Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PostGIS attribute table annoyance #12128

Closed
qgib opened this issue Nov 8, 2009 · 6 comments

Comments

@qgib
Copy link
Contributor

commented Nov 8, 2009

Author Name: Ivan Mincik (Ivan Mincik)
Original Redmine Issue: 2068
Affected QGIS version: master
Redmine category:digitising


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.

@qgib

This comment has been minimized.

Copy link
Contributor Author

commented Jun 11, 2010

Author Name: Paolo Cavallini (@pcav)


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

@qgib

This comment has been minimized.

Copy link
Contributor Author

commented Jun 11, 2010

Author Name: Ivan Mincik (Ivan Mincik)


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.

@qgib

This comment has been minimized.

Copy link
Contributor Author

commented Dec 16, 2011

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was changed from Version 1.7.0 to Version 1.7.4
@qgib

This comment has been minimized.

Copy link
Contributor Author

commented Apr 16, 2012

Author Name: Paolo Cavallini (@pcav)


  • crashes_corrupts_data was configured as 0
  • version was configured as master
  • fixed_version_id was changed from Version 1.7.4 to Version 1.8.0
@qgib

This comment has been minimized.

Copy link
Contributor Author

commented Sep 4, 2012

Author Name: Paolo Cavallini (@pcav)


  • fixed_version_id was changed from Version 1.8.0 to Version 2.0.0
@qgib

This comment has been minimized.

Copy link
Contributor Author

commented Jun 2, 2014

Author Name: Nathan Woodrow (@NathanW2)


The attribute table has been reworked a bit since 1.7, and I can't reproduce on master. Please reopen if still happening for you.


  • assigned_to_id removed nobody
  • resolution was configured as fixed/implemented
  • status_id was changed from Open to Closed
  • pull_request_patch_supplied was configured as 0
@qgib qgib added this to the Version 2.0.0 milestone May 24, 2019
@qgib qgib closed this May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.