I'm constructing some gigantic (as in several 100MBs) insert
statements. I'd now like to execute them using SOCI. Ideally SOCI
would do as little work as possible and just forward the query to
the database. Unfortunately that is not the case. SOCI copies the
statement (multiple times?) in order to be able to execute it in a
destructor (final_action()).
Questions:
1) what's the fastest way to execute such queries using SOCI?
2) can I somehow get to the native executeQuery mechanism via the
backends?
3) can I control the query lifetime and number of copies SOCI makes?
I know I could be using statement.execute() multiple times using
prepared statements but our benchmarks seem to indicate that
chunking into huge batches is faster.
I'm using mySQL and PostgreSQL backends in case it matters.
best regards,
Sören
--
Sören Meyer-Eppler
software developer
[email protected]
http://www.BuschnicK.net
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Soci-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/soci-users
