> I want to save a very long list of object (more than 2000 elements) with ORMLite.
> It's very long. I think it's due to ORMLite create one transaction for each "create(Object object)", isn't it ?
No. ORMLite does not create a transaction at all unless you ask for them using the transaction manager. The problem most likely is that most databases are un "auto-commit" mode. That means that they synchronize to storage on every call. I would suggest you look into the batch operations dao method:
Here's some more data:
http://ormlite.com/docs/transactions
If you put all of your inserts inside of the call() method than it will turn off auto-commit, start a transaction, and then commit the transaction when call() returns and restore the auto-commit setting.
gray