Any idea why this code is not working for me? Everything seems to be fine. When I include this within transaction, it seems to work!!!

AnnotationConfiguration cfg = new AnnotationConfiguration();
cfg.setProperty("hibernate.dialect", "org.hibernate.dialect.InterbaseDialect");
cfg.setProperty("hibernate.connection.url", "jdbc:firebirdsql:localhost:D:\\FireBirdDB\\mydb.gdb");
cfg.setProperty("hibernate.connection.username", "sysdba");
cfg.setProperty("hibernate.connection.password", "masterkey");
cfg.setProperty("hibernate.connection.driver_class", "org.firebirdsql.jdbc.FBDriver");
cfg.setProperty("hibernate.c3p0.min_size", "5");
cfg.setProperty("hibernate.c3p0.max_size", "20");
cfg.setProperty("hibernate.c3p0.timeout", "1800");
cfg.setProperty("hibernate.c3p0.max_statements", "50");
cfg.setProperty(Environment.HBM2DDL_AUTO, "create-drop");
cfg.setProperty("hibernate.show_sql", "true");
cfg.addAnnotatedClass(Company.class);
SessionFactory sf = cfg.buildSessionFactory();

Session s = sf.openSession();
try {
Company TC = new Company();
TC.setName("aa");
s.save(TC);

Company TC1 = new Company();
TC1.setName("bb");
s.save(TC1);
} catch (Exception e) {
throw e;
} finally {
s.flush();

}

What?

Im sorry, i did not understand your question. You did not understand what ny question was OR was it something else?

I wonder why you don't fill out the form in the textarea.

I am sorry. I think you ment that you wanted the code to be pasted in a more readable form. I am learning to use the tool bar. Repasting the code again.

Your question is confusing. I assume that what you are saying is that the code works when embedded within a transaction but doesn't when no transaction demarcation is declared. This comes as no surprise to us.

From the hibernate reference manual:

Sorry, I missed s.close() AFTER s.flush();. But eitherways here I flush it and then close it, which should automatically commit (even if I am not using Tx). Should this suffice?

No, because nowhere are you managing the state of the transaction. Sometimes I think auto-commit has corrupted java developers. In SQL you cannot just perform a DML operation and expect it to "stick" without a transaction.