Thank you for the heads up.
I choose ZeosLib, mainly due to my benchmarking results (using mORMot) : ZeosLib > FireDAC > UniDAC. ZeosLib has amazing performance indeed (see below)
I don't expect Aurelius to have the same performance as mORMot. Aurelius ORM design better suits my needs than mORMot, with its ease of use and learn. I do expect Aurelius to have a balanced performance versus ORM ease of use.
- That being said, it would be great if Aurelius can give some priority to ZeosLib, and optimize its ZeosLib-based batch insert. ZeosLib has better performance than FireDAC, overall.
Would you consider improving the Aurelius/ZeosLib batch performance in Aurelius 5?
P.S. What is the expected/estimated release date for Aurelius 5?