Hi friends,
Last weekend I made an environment that use a MySQL Server version 4.1 that
was defined to be the MASTER and other one version 5.1 defined as SLAVE.
Because the application that was concept working over exception, often the
SLAVE server got new error and replication stops.
Well, I
Hi Wagner,
You have to start the server with the option as below for skipping the
error.
--slave-skip-errorr= 1062 or all
1062 - will skip the your error as the error number is 1062 and all will
skip all the errors.
You have to mention specific error numbers to skip the same.
--
Thanks
Ok, Suresh. . .I started MySQL with slave_skip_errors = all and It solve the
problem!
Thanks.
WB
2010/1/25 Suresh Kuna sureshkumar...@gmail.com
Hi Wagner,
You have to start the server with the option as below for skipping the
error.
--slave-skip-errorr= 1062 or all
1062 - will skip the
In innodb, is it possible to have an auto_increment field without
making it a (part of a) primary key? Why is this a requirement? I'm
getting the following error. Thanks in advance.
ERROR 1075 (42000): Incorrect table definition; there can be only one
auto column and it must be defined as a key
it's not an innodb thing:
http://dev.mysql.com/doc/refman/5.0/en/create-table.html
Note
There can be only one AUTO_INCREMENT column per table, it must be indexed, and
it cannot have a DEFAULT value. An AUTO_INCREMENT column works properly only if
it contains only positive values. Inserting a
Right, I saw the docs. I'm fine with creating an index on it, but the
only way I've successfully created a table with auto_increment is by
making it a primary key. And I still don't understand why this
requirement is there in the first place.
On Mon, Jan 25, 2010 at 10:32 AM, Tom Worster
2010/1/25 Yang Zhang yanghates...@gmail.com:
Right, I saw the docs. I'm fine with creating an index on it, but the
only way I've successfully created a table with auto_increment is by
making it a primary key. And I still don't understand why this
requirement is there in the first place.
The requirement is that it be indexed. The index need not be a primary key.
mysql create table t (i int not null auto_increment, index(i)) engine innodb;
Query OK, 0 rows affected (0.45 sec)
On Jan 25, 2010, at 9:39 AM, Yang Zhang wrote:
Right, I saw the docs. I'm fine with creating an index
I have a server with 16Gb of RAM and a dual-core 2Ghz processor. It is
running the latest mysql-server from debian lenny (5.0.1). I have databases
for drupal, moodle, spamassassin, horde3, and a small database for
departmental stuff.
The problem is that inserts/updates are sometimes very slow,
I don't get it... I mean, I get the concept -- it's a crontab; but why
would someone opt to put these events here instead of in the God-given
CRONTAB as everything else in the system uses? This just seems like one
more place to forget about a query/code and have unexpected things
happen.
We
2010/1/25 John G. Heim jh...@math.wisc.edu:
I have a server with 16Gb of RAM and a dual-core 2Ghz processor. It is
running the latest mysql-server from debian lenny (5.0.1). I have databases
for drupal, moodle, spamassassin, horde3, and a small database for
departmental stuff.
The problem
yah, mysql only allows one auto increment field n that's used as the
primary key in tables. I don't think it has to be the primary key as
long as it is a unique key i think that's okay.
so u should be able to do : create table (myid int unsigned not null
auto_increment., unique key (myid));
In the last episode (Jan 25), Daevid Vincent said:
I don't get it... I mean, I get the concept -- it's a crontab; but why
would someone opt to put these events here instead of in the God-given
CRONTAB as everything else in the system uses? This just seems like one
more place to forget about a
13 matches
Mail list logo
