On Nov 29, 2009, at 3:52 PM, Jacek Kałucki wrote:

> It can't be done, because every field, even with None/Null value is
> passed to INSERT command.


        It's not supposed to work that way. Only values that were changed  
after the new record was created are supposed to be passed; the  
"blank" values are supposed to be ignored.

        The reason for the blanks is that a record in Python is a dict, with  
column names as the keys. There is no way to have a key without a  
value, and in order to be able to be edited with UI controls, we need  
to supply a value of the same type as the column.

        I think that the way it should work for new, unsaved records is as  
follows:

modified: used to determine isChanged(), and included in INSERT.
default: not used to determine isChanged(), but included in INSERT.
blanks: not used to determine isChanged(), and not included in INSERT.

        This will take some additional work, so I thought I'd run this  
delineation by everyone first. If this sounds good, we can take the  
discussion over to dabo-dev.


-- Ed Leafe



_______________________________________________
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/[email protected]

Reply via email to