Hello;
i give you an example of my problem,
i have a list that contains 10000 object, i tried to commit this list in one transaction but the problem is for example if the object number 1000 that contains a duplicate key i find that transaction is rollback and the 999 first objects are persisted in the database.
i want a solution when i find an object that contains a duplicate key i rollback the transaction and don't store any object in the database (mongodb)

Here my function to store object in the database:


javax.transaction.TransactionManager tx = com.arjuna.ats.jta.TransactionManager.transactionManager();
ArrayList<MesureparamNo> listNoSQL = new ArrayList<MesureparamNo>();
tx.begin() ;
MesureparamNo mes = new MesureparamNo();
for(i=1;i<10000;i++)
{
MesureparamNo mesure = new MesureparamNo();
listNoSQL.add(mesure);
}
for (Iterator<MesureparamNo> itt = listNoSQL.iterator(); itt.hasNext();) {
MesureparamNo enquiry = itt.next();
try{
HibernateUtilNoSQL.getEntityManager().joinTransaction();
HibernateUtilNoSQL.getEntityManager().persist(enquiry);

}catch(Exception re){
tx.rollback();
throw re;
}

}
try{
tx.commit();
}
catch(Exception re){
tx.rollback();
throw re;
}

Hi,

Because MongoDB itself does not support transaction, what you are asking is not likely to be doable (for MongoDB at least). Some have explored compensation based transactions for document stores but that is still early stage and a bit ad hoc.

What we plan to have is an error report API that would tell you which inserts have worked and which have not. Based on that, you will be able to manually decide to undo the inserts for example. The issue targeting that feature is https://hibernate.atlassian.net/browse/OGM-465

Thanks Emanuel for your answer.
I test the same code with a database SQL(PostgreSQL) which support the transaction using hibernate, i find the same problem of persisting data.So, i think that the problem is not only for Mongodb(NoSQL).
So my question is if my solution is doable with SQL database.if yes which database can support my solution SQL or NoSQL?
thanks

Yes that should definitely work.
The next best guess is that the persistence.xml is misconfigured and that the transaction manager and Hibernate are not linked together. So your tx would be rollbacked but contain nothing in the first place whereas the persist would be out of tx and thus committed right away.
Or it could be something in your framework (HibernateUtilNoSQL or test framework).