On 5-9-2013 16:45, Jim Starkey wrote: > The keys to reducing round trips are to bundle metadata with data to > eliminate the need for "info" trips and, most importantly, to batch > record retrievals and batch inserts into single large packets. Sending a > MB worth of records is obviously a great win. So is implementing the > equivalent of the JDBC batch update semantics.
I was wondering about that: the format of the op_execute message, and specifically the p_sqldata structure and its p_sqldata_messages field, suggest it could be used to pass multiple value messages (parameter sets) and thus support batched updates (similar to how op_fetch returns multiple rows of data with the same message structure). This would preferably send a response with per parameter set statement statistics (eg updates/deletes) to support the information requirements like in JDBC (affected rows per successfully executed parameter set). Mark -- Mark Rotteveel ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
