SFieldReference/overlapping keys

Frank,

Please check carefully what I have done to 
SFieldReference.innerRawSetFieldValue and SFieldScalar.innerRawSetFieldValue.

I think it is now correct, but it is not properly tested.

(The idea of passing down the old value to validate field was a bad 
one, and I took it out.  The problem is that the old value is not 
available at validateRecord time.  But do we really want to validate 
fields at record time, maybe the should only and always be immediate?)

I would also like to move to the .Net convention of prefixing all 
event methods that are designed to be overridden by the user with 
"on", eg. onValidateRecord rather than validateRecord.  We should 
never place any code in an "on" method in case the user forgets to 
call super().  That might be a good next task.

I am going to bed.

Where do you live?  I vaguely recall France.

We should also start posting this to the SimpleOrm list.

Regards,

Anthony


Dr Anthony Berglas, [email protected]       Mobile: +61 4 4838 8874
Just because it is possible to push twigs along the ground with ones nose
does not necessarily mean that is the best way to collect firewood.


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/SimpleORM/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/SimpleORM/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/