Hello Jim,
> On Thu, Apr 10, 2008 at 09:32:43AM +0200, Martijn Tonies wrote:
> > It seems that SHOW ENGINES fails on MySQL 5.0.51a (community edition
> > checked).
> >
> > Instead of returning the full data, the first two columns are cut off at
3
> > characters,
> > while the "comment" column is
Hi,
what are the different test cases to test MySQL Master and Slave Replication
Database Server.
Thanks and Regards
Kaushal
On Thu, 2008-04-10 at 11:43 -0500, Paul DuBois wrote:
>
> For each corresponding table:
>
> INSERT INTO db1.mytable SELECT * FROM db2.mytable;
>
> --
> Paul DuBois, MySQL Documentation Team
> Madison, Wisconsin, USA
> MySQL AB, www.mysql.com
>
That is exactly what I was looking for. Thank
At 1:09 PM -0400 4/10/08, Christoph Boget wrote:
> > I have a slew of records that went to the wrong database. The tables
> have the same names and now I want to copy those records over to the
> correct database. Is there such a mechanism using the cli mysql
> application in Linux?
For e
Yes
Regards,
Jerry Schwartz
The Infoshop by Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
www.the-infoshop.com
www.giiexpress.com
www.etudes-marche.com
-Original Message-
From: Christoph Boget [mailto:[EMAIL PROTECTED]
Sent: T
> > I have a slew of records that went to the wrong database. The tables
> > have the same names and now I want to copy those records over to the
> > correct database. Is there such a mechanism using the cli mysql
> > application in Linux?
> For each corresponding table:
> INSERT INTO db1.mytab
> I have a slew of records that went to the wrong database. The tables
> have the same names and now I want to copy those records over to the
> correct database. Is there such a mechanism using the cli mysql
> application in Linux?
If the tables have the same schema, you should be able to jus
At 12:21 PM -0400 4/10/08, Larry Brown wrote:
I have a slew of records that went to the wrong database. The tables
have the same names and now I want to copy those records over to the
correct database. Is there such a mechanism using the cli mysql
application in Linux?
For each corresponding
> I have a slew of records that went to the wrong database. The tables
> have the same names and now I want to copy those records over to the
> correct database. Is there such a mechanism using the cli mysql
> application in Linux?
If the tables have the same schema, you should be able to jus
I have a slew of records that went to the wrong database. The tables
have the same names and now I want to copy those records over to the
correct database. Is there such a mechanism using the cli mysql
application in Linux?
Larry
--
MySQL General Mailing List
For list archives: http://lists.
On Thu, Apr 10, 2008 at 09:32:43AM +0200, Martijn Tonies wrote:
> It seems that SHOW ENGINES fails on MySQL 5.0.51a (community edition
> checked).
>
> Instead of returning the full data, the first two columns are cut off at 3
> characters,
> while the "comment" column is cut off at 26 characters.
I am having what I think is a weird problem. Here's my setup:
- Im running Windows Vista.
- I've tried the exact same thing on Linux with the exact same result.
- I'm running the mysql CLI. The client is 5.0.45-community on the Vista
system, 4.1.22 on the Linux system.
- The server in both cases
> [EMAIL PROTECTED] wrote:
>>
>> Does this sound about right? Anybody see any road hazards? If not, and
>> this line of thinking is reasonable, should the DB with the older
records
>> also be replicated so that when a new old records table needs to be
>> created, I don't have to repeat everythin
Hi all,
You can read this article, written by a SUN benchmarking guru (hi
Dimitri :) ).
Best regards.
Web link : http://dimitrik.free.fr/db_STRESS_BMK_Part2_ZFS.html
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PR
Sorry, a bit too hasty --
It seems to work fine in the command line client!
Has the wire protocol changed somehow?
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.
Hi,
It seems that SHOW ENGINES fails on MySQL 5.0.51a (community edition
checked).
Instead of returning the full data, the first two columns are cut off at 3
characters,
while the "comment" column is cut off at 26 characters.
Sample output:
# | Engine| Support| Comment
--+---+
16 matches
Mail list logo