Glom 1.8.1: list view: 2 records added instead of 1.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| glom (Ubuntu) |
Undecided
|
Unassigned |
Bug Description
Binary package hint: glom
Create a new database.
Create a table and enter to acept defaults fields.
Be sure you are in "List" view.
Leave the ID field blank.
For the first record:
Click and enter a value in Description.
Press enter to accept.
Click and enter a value in Comments.
Hit enter to accept.
For the second second:
Click and enter a value in Description.
Press enter to accept.
Click and enter a value in Comments.
Press enter to accept.
For the third record:
Click and enter a value in Description.
Hit enter to accept.
Click and enter a value in Comments.
Press enter to accept.
We have three records.
Exit Glom.
Open the database.
We have 5 or 6 records!!!
I think that each time I hit the "enter key", a new record is created.
See the ID field each time press enter key.
Related branches
Murray Cumming (murrayc) wrote : | #1 |
Murray Cumming (murrayc) wrote : | #2 |
Fixed by this commit in the svn trunk and 1.8 branches:
2008-11-24 Murray Cumming <email address hidden>
* glom/utility_
user_added(): Call set_value_key(), like the old code did.
Otherwise, each field edit adds another record, generating a new primary
key each time, resulting in duplicate records.
Ubuntu bug https:/
(elmergato)
Changed in glom: | |
status: | New → Fix Committed |
Launchpad Janitor (janitor) wrote : | #3 |
This bug was fixed in the package glom - 1.8.5-0ubuntu1
---------------
glom (1.8.5-0ubuntu1) jaunty; urgency=low
* New upstream release (LP: #256701), fixes LP bugs:
+ Clear the text in property dialogs for text items (LP: #309147)
+ Don't crash when showing and then hiding the grid (LP: #303453)
+ Temporarily remember the sort order so it is the same when navigating
away and back (LP: #303422)
+ Use the list's sort order for the top-level records in the report
(LP: #303425)
+ Users/Groups: Disable drag-and-drop for the treeview, because it is
useless and confusing (LP: #299573)
+ Import: Sort the fields list alphabetically (LP: #306593)
+ delete primary key make unusuable the database (LP: #299549)
+ Spanish translate incomplete (LP: #299556)
+ import date format error (LP: #299591)
+ can't delete data from table list view (LP: #299853)
+ Field definition: default value not saved (LP: #299896)
+ reports crashing (LP: #300054)
+ Year error with date fields (LP: #300057)
+ list view: 2 records added instead of 1 (LP: #300819)
* debian/control: Refreshed dependencies for libglom-dev.
* debian/control: Updated build-deps to match configure checks. goocavnasmm
build-dep bumped to version without .la files.
* debian/rules: Don't delete the directory containing the templates.
* debian/control, debian/rules, debian/glom-doc.*: Split out
arch-
is now recommended by glom (glom will still work if they're not available)
* debian/copyright: Rewritten to new machine-readable format.
-- Iain Lane <email address hidden> Sun, 11 Jan 2009 17:12:01 +0000
Changed in glom: | |
status: | Fix Committed → Fix Released |
Yes, editing a field on a just-entered record adds a new record, even if the record already has a primary key (meaning, it was already added). That's a serious bug. I'll fix it.