Re: SimpleORM 3.11: Fails to create m:n relation record

Good point, same solution, use setDirty.  

I think that it would be wrong for findOrCreate to magically create records just because you looked at them.  And certainly making key only or initialized only a special case is not on.  But there is a real question whether create should always mark dirty -- probably should but I would not change that until a major update.  Maybe we could add createAlways, or just create2 and deprecate create?

Regards,

Anthony

At 11:42 PM 18/02/2010, Roland Tapken wrote:
>Hello Anthony,
>
>>Key only records are actually rare in practice.  There is almost always something that you want to set on the m:n record.  Eg. who or when or why is the article in a certain category, or a user comment as to why.
>
>The same problem occurs when all fields are defined using setInitialValue(). I think this is very awkward because (when using findOrCreate) the record will be discarded silently if the user does not change any value.
>
>Regards,
>
>Roland

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