need of flush() with commit() in one-to-many association?

anilkumar · **Posted:** Thu May 26, 2005 5:16 am

hi,
I request somebody to answer to my doubt ("need of flush() with commit() in one-to-many associations")as early as possible.
regards,
anil

pstruhos · **Joined:** Fri Nov 21, 2003 10:23 am **Posts:** 81

basically there is no need to flush before commit because commit will do it

anilkumar · **Posted:** Thu May 26, 2005 9:53 am

hi,
Thanks for ur reply.
I have even done that and I have clearly mentioned about it in my issue.As I said I have tried commit() with out flush() but the data is not being persisted in the database.So finally I have done both flush() and commit() .
So u pls give me someother effecitve solution.
regards,
anil

pstruhos · **Joined:** Fri Nov 21, 2003 10:23 am **Posts:** 81

Are you using hibernate standalone or with application server?

pstruhos · **Joined:** Fri Nov 21, 2003 10:23 am **Posts:** 81

Code:

        Session s = ....
        
        Product product = new Product();
        product.setId(new Long(1));
        product.setName("xxx");
        product.setDescription("xxx ");

        s.saveOrUpdate(product);
        s.connection().commit();

note: in managed envoronment do flush and close (not commit)

SeJo · **Joined:** Thu Sep 16, 2004 4:36 am **Posts:** 22

anilkumar,

if you commit yourself, don't forget to set session.setFlushMode(FlushMode.COMMIT);

anilkumar · **Posted:** Fri May 27, 2005 1:59 am

mr sejo,
may I know why do we need to explicitly set the FLUSHMODE to commit.Because there is a chance that this setting may expose us to stale data i.e,modifications we we will make to the objects only in memory may conflict with the results of the query.
So I hope that u will give me some other effective solution for my issue that I had posted.
regards,
anil