[nhibernate-issues] [JIRA] Closed: (NH-853) Inconsistent need of the Flush method invokation

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-853?page=3Dall ]
    =20
Sergey Koshcheyev closed NH-853:
--------------------------------

    Resolution: Not an Issue

This is not an issue with NHibernate, NH has to perform identity inserts ri=
ght away to be able to return an identifier to you. Even in that case, you =
are advised to call Flush explicitly.

> Inconsistent need of the Flush method invokation
> ------------------------------------------------
>
>          Key: NH-853
>          URL: http://jira.nhibernate.org/browse/NH-853
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.2.0.Beta2
>     Reporter: Andr=C3=A9s G. Aragoneses
>     Priority: Trivial
>  Attachments: NHibBugAboutFlush.zip
>
> I have managed to create a simple NHibernate testcase which creates some =
objects and all the operations are done successfully without the FLUSH meth=
od invokation *except* the many-to-many relation creations.
> I am attaching the testcase as a VS2005 solution. Note the following line=
 in Program.cs:
>             //if this line is commented, the table TERMINALS_TERMINALGROU=
PS is not persisted! but the rest yes
>             oSession.Flush();
> P.S.: Be sure to add the NHibernate DLL's to the 'Lib' directory (and to =
the bin/Debug ones) when uncompressing.
> P.S.2: Don't pay attention to the name of the solution. It's for another =
bug I am going to open.

--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira