Eventually, I've got my lesson. Because it might be of some interest for the beginner:
1)Use the associated sqlite3_bind_* variants for your data. I did make a mistake in converting forth and back to strings beforehand. 2)It broke my program design a bit, but setting up large STL vector based C++ string records (especially using push_back and stringstreams for conversions) turned out to be a show stopper on some platforms. The plan was, to feed them to sqlite_bind* later on (with the additional performance drop caused by exclusively using sqlite3_bind_text mentioned above). Setting up the structures took more time than the asynchronous writing to the database. This way my 40 minutes per 25M rows dropped to 8 minutes, something I'm completely happy with. I'm sure, many things are quite standard for the experts here, but for the beginner it might be useful to know. I have seen a Wiki item, dealing with performance. Would it be possible to give some emphasis to the problem in the standard documentation too ? Thank you for the software, Richard (et al ?). I like the library a lot. Micha --
