Tom Cunningham [EMAIL PROTECTED] wrote:
In short: what is the standard MySQL handling of temporary tables,
*especially* when you've got a slave filter on to only replicate certain
tables?
These options apply to the temporary tables too.
My replication stopped over the weekend, because
Hi,
In short: what is the standard MySQL handling of temporary tables,
*especially* when you've got a slave filter on to only replicate certain
tables?
My replication stopped over the weekend, because a query was executed
which created temporary tables, then used that table to update one of
On 26 Feb 2002, Arjen Lentz wrote:
On Tue, 2002-02-26 at 12:21, Peter Jennings wrote:
We have been trying to solve a replication issue related to TEMPORARY
tables.
Here's the issue
Every three hours we run a processX (C++ compiled program) on the Master
mysql that goes something
We have been trying to solve a replication issue related to TEMPORARY
tables.
Here's the issue
Every three hours we run a processX (C++ compiled program) on the Master
mysql that goes something like this:
CREATE TEMPORARY TABLE tempTableA
INSERT INTO tempTableA
INSERT INTO normalTableB
Hi Peter,
On Tue, 2002-02-26 at 12:21, Peter Jennings wrote:
We have been trying to solve a replication issue related to TEMPORARY
tables.
Here's the issue
Every three hours we run a processX (C++ compiled program) on the Master
mysql that goes something like this:
CREATE TEMPORARY
Is there any reason why I shouldn't create temporary tables on a slave
server? The tables only last until the client closes its connection,
they aren't visible to other clients.
I don't do any
INSERT INTO permanentTable SELECT ... FROM temporaryTable
On Mon, Aug 20, 2001 at 02:04:09PM -0500, Mike Wexler wrote:
Is there any reason why I shouldn't create temporary tables on a
slave server? The tables only last until the client closes its
connection, they aren't visible to other clients.
I don't do any
INSERT INTO permanentTable
