Ticket #1132 (new defect)

Opened 4 years ago

Last modified 1 year ago

Unchanged values not saved with new()

Reported by: aklaver Assigned to: somebody
Priority: major Milestone: 0.9
Component: ui Version: 0.8.3
Keywords: Cc:

Description

When calling save() after a new() only values that have changed are included in the INSERT
statement. This occurs even with SaveNewUnchanged?=True.

Attachments

dabo_test.sql (14.5 kB) - added by aklaver on 01/28/08 09:06:26.
Postgres dump of table dabo_test
dabo_test.cdxml (7.7 kB) - added by aklaver on 01/28/08 09:07:10.
Class Designer file
dabo_test-code.py (1.2 kB) - added by aklaver on 01/28/08 09:07:26.
Class Designer code file

Change History

01/15/08 08:29:24 changed by uwe_grauer

  • milestone changed from 0.8.3 to 0.9.

Adrian, please add a testcase because other people did get different results from their tests regarding this issue.

01/28/08 09:06:26 changed by aklaver

  • attachment dabo_test.sql added.

Postgres dump of table dabo_test

01/28/08 09:07:10 changed by aklaver

  • attachment dabo_test.cdxml added.

Class Designer file

01/28/08 09:07:26 changed by aklaver

  • attachment dabo_test-code.py added.

Class Designer code file

01/28/08 09:07:40 changed by aklaver

Attached files for test case. dabo_test.sql is Postgres 8.2 dump of test table and data. dabo_test.cdxml and dabo_test-code.py where generated from ClassDesigner? ~3849 The control of interest are plant_type(RegID PlantType?) and season(RegID Season). Field common is not null and needs an entry. If you do Ctrl-D self.new() you will see they have values in the displayed form as well as part of the control i.e PlantType?.value yields a value. When you do self.save() the values are not saved.

02/03/11 10:15:39 changed by paul

Is this still an issue?