Ed Leafe wrote:
> On Jan 14, 2008, at 10:46 PM, Adrian Klaver wrote:
>
>> Before I go any further I want to make I understand
>> SaveNewUnchanged. If it is
>> set to False (the Default setting) , when one saves a new record
>> only the
>> field values in the ui that were entered by hand or changed are
>> saved. If it
>> is set to True all values in a new record are saved. Even though I
>> have
>> SaveNewUnchanged = True it is acting like =False. In other words
>> though the
>> values for each Dropdown List is set it not being picked up the
>> process the
>> builds the INSERT query. At this point I know this is what is
>> happening or
>> not happening as the case may be. I would suggest creating a test
>> form with
>> Dropdown lists and try it for yourself.
>
> You might be correct that unchanged default values are not saved.
> The memento system determines values that have changed from their
> defaults and constructs the insert/update statement from those
> changed fields. SaveNewUnchanged will override the behavior of
> discarding a new, unchanged record, but the insert statement will
> still be constructed using only changed fields.
>
> Please enter a ticket for this, as I do not have the time right now
> to fix this.
>
I tested this too.
My default values in the bizobj:
self.DefaultValues['gebdat'] = None
self.DefaultValues['e_sex'] = 20002
I only changed the field vorname in my form.
In my database log i see this:
insert into JNP (name, bem, iid, vorname, gebdat, e_per, e_sex) values
('', '', 1000063, 'a', NULL, 0.00, 20002)
As you can see gebdat and e_sex got saved.
Uwe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
