Re: implicit commit

Hi,

yes, if you do a session.query(qry), an implicit flush is made.

You can use session.queryNoFlush(qry) to explicitely ask SimpleOrm not
to flush (but of course your current dataset won't be taken into account
for the query result).

HTH,

Franck

Le mardi 14 décembre 2010 à 07:49 +0100, Guenter Wildmann a écrit :
>   
> Hello!
> 
> I observed the following behavior which i consider as bug:
> 
> If i create a record for a table which has an attribute with the
> mandatory-flag set and not declaring a value for this attribute (for
> the
> moment) i get a null-value exception if i do a query on some
> completely
> different table (even if this query is read-only).
> 
> So it seems to me, the framework does some implicit pre-commit while
> executing the query and therefore complains about the attribute not
> set.
> 
> Ciao, Guenter
> 
> 
> 
> 
> 

-- 
Franck Routier 
             Logo Axège
Axège
23,rue Saint-Simon
63000 Clermont-Ferrand
Tél: +33 (0)4 63 05 95 40
Fax: +33 (0)4 73 70 65 29
Email: [email protected]






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

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/