On Tue, Jun 29, 2004 at 08:46:35PM -0400, Alejandro Heyworth wrote:
> Eric,
>
> I'm looking for a way to eliminate the construction, transmission, and
> parsing of the long multi-row INSERT queries that we are issuing from our
> client app. Since we are inserting 200k rows a shot, we're looking
Eric,
I'm looking for a way to eliminate the construction, transmission, and
parsing of the long multi-row INSERT queries that we are issuing from our
client app. Since we are inserting 200k rows a shot, we're looking for
every boost that we can find.
* Connecting: (3) [want to use a connect
http://dev.mysql.com/doc/mysql/en/Insert_speed.html
-Eric
On Tue, 29 Jun 2004 09:43:04 -0400, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> I am proposing this as a hypothetical situation and I would like the full
> feedback of the group:
>
> Could Alejandro re-use the sections of the MyS
I am proposing this as a hypothetical situation and I would like the full
feedback of the group:
Could Alejandro re-use the sections of the MySQL source code that handle
replication and bin-logging to make his data capture application appear as
a "Master" server and have his MySQL database act as
Shawn,
Very Interesting idea. I definitely want to look into this a bit more.
I fear though that the bin-logs might be written first to disk before they
are copied over to the replicas.
Another member of my team mentioned there might be a way to issue direct
MyISAM table INSERTS. She suggested
