Hi.
You can show us your show create table statement as well.
杨涛
我博客1:http://yueliangdao0608.cublog.cn
My 我博客2:http://yueliangdao0608.blog.51cto.com
2010/12/20 Xavier Correyeur x.correy...@free.fr
Hi everybody !
A have a discontinued AUTO_INCREMENT sequence when i insert data in a table
Too curious...could you share a SHOW CREATE TABLE from this table as
requested before?
Best regards.
--
Wagner Bianchi
2010/12/21 杨涛涛 david.y...@actionsky.com
Hi.
You can show us your show create table statement as well.
杨涛
我博客1:http://yueliangdao0608.cublog.cn
My
...@free.fr; mysql@lists.mysql.com
Sent: Tue, 21 December, 2010 3:28:00 PM
Subject: Re: Discontinued AUTO_INCREMENT problem
Too curious...could you share a SHOW CREATE TABLE from this table as
requested before?
Best regards.
--
Wagner Bianchi
2010/12/21 杨涛涛 david.y...@actionsky.com
Hi.
You
Sent: Tue, 21 December, 2010 3:28:00 PM
Subject: Re: Discontinued AUTO_INCREMENT problem
Too curious...could you share a SHOW CREATE TABLE from this table as
requested before?
Best regards.
--
Wagner Bianchi
2010/12/21 杨涛涛 david.y...@actionsky.com
Hi.
You can show us your show
Hi everybody !
A have a discontinued AUTO_INCREMENT sequence when i insert data in a
table with a 100 (or more) items SELECT request.
The problem (or situation) is reproductible, you can see an example below.
Anybody could explain this to me ?
Cheers
XC
My MySQL version : Ver 14.14 Distrib
alter table tablename modify id int not null auto_increment primary key;
On Sat, Oct 25, 2008 at 2:48 AM, Paul [EMAIL PROTECTED] wrote:
Anybody know if there's a way to change a primary key field that is not
auto-incremented, turning on auto-increment but preserving the values that
are
Anybody know if there's a way to change a primary key field
that is not auto-incremented, turning on auto-increment but
preserving the values that are currently in it?
TIA,
Paul W
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
InterNetX - Andreas Prasch wrote:
Hi,
I have a master and a slave mysql server. On the master I write binlogs
needed for replication. From time to time I have chronological
auto_increment problems, here's a short explanation.
- the table structure :
| Field | Type| Null | Key | Default |
Hi,
I have a master and a slave mysql server. On the master I write binlogs
needed for replication. From time to time I have chronological
auto_increment problems, here's a short explanation.
- the table structure :
| Field | Type| Null | Key | Default | Extra |
So, if I understand you correctly, somewhere in the middle of a 20,000 row
insert, a row gets inserted with auto_increment id = 87,123,456, say, then
the next row tries to insert with the value 87,123,457 but fails. You fix
this by skipping the next value with
ALTER TABLE yourtable
On Jun 23, 2004, at 8:15 AM, Michael Stassen wrote:
So, if I understand you correctly, somewhere in the middle of a 20,000
row insert, a row gets inserted with auto_increment id = 87,123,456,
say, then the next row tries to insert with the value 87,123,457 but
fails. You fix this by skipping
On Jun 18, 2004, at 5:31 PM, Scott Haneda wrote:
While I do not know why, I would suggest you simply drop the PK and
recreate
it, this should be a whole lot faster than the alter.
This took the same amount of time as the alter table (a little longer
actually). The documentation says that in
At 13:37 -0400 on 06/19/2004, Michael Stassen wrote about Re:
AUTO_INCREMENT problem... ER_DUP_ENTRY? (No, it's not a:
Finally, just to cover all the bases, that really is 87 million inserts, not
8.7 million, right? I only ask because a MEDIUMINT column runs out a little
past 8.3 million
Robert A. Rosenberg wrote:
At 13:37 -0400 on 06/19/2004, Michael Stassen wrote about Re:
AUTO_INCREMENT problem... ER_DUP_ENTRY? (No, it's not a:
Finally, just to cover all the bases, that really is 87 million
inserts, not
8.7 million, right? I only ask because a MEDIUMINT column runs out
Just a suggestion, Kevin, but how about changing from INT to BIGINT?
Terry
--Original Message-
We have a table with a primary index which is INT NOT NULL
AUTO_INCREMENT.
After inserting ~87,000,000 entries, we started seeing error 1062,
ER_DUP_ENTRY.
We can get
would suggest you simply drop the PK and
recreate
it, this should be a whole lot faster than the alter.
Thanks, I'll give it a try next time the problem shows up.
My main worry is that the AUTO_INCREMENT problem is merely a symptom of
a more serious problem with the table. I've got a couple
On Jun 19, 2004, at 6:03 AM, Terry Riley wrote:
Just a suggestion, Kevin, but how about changing from INT to BIGINT?
I thought of trying that, but since we're nowhere near the limit even
for an INT I think changing to BIGINT is premature. I want to find out
a bit more about what's happening
To the best of my knowledge, AUTO_INCREMENT columns are limited only by the
size of the int, so an INT NOT NULL AUTO_INCREMENT should go to 2,147,483,647.
Something about your description doesn't quite fit, however. You say that
you are nowhere near the limit, but you say that resetting the
On Jun 19, 2004, at 10:37 AM, Michael Stassen wrote:
Something about your description doesn't quite fit, however. You say
that you are nowhere near the limit, but you say that resetting the
auto_increment starting point fixes the problem. Those seem
contradictory to me.
To me as well, that's
At 17:16 -0700 on 06/18/2004, Kevin Brock wrote about AUTO_INCREMENT
problem... ER_DUP_ENTRY? (No, it's not a one:
We have a table with a primary index which is INT NOT NULL
AUTO_INCREMENT.
After inserting ~87,000,000 entries, we started seeing error 1062,
ER_DUP_ENTRY.
You are wasting half your
We have a table with a primary index which is INT NOT NULL
AUTO_INCREMENT.
After inserting ~87,000,000 entries, we started seeing error 1062,
ER_DUP_ENTRY.
We can get going again after doing an ALTER TABLE to reset the
auto_increment starting point, but this takes about an hour...
I've seen
on 06/18/2004 05:16 PM, Kevin Brock at [EMAIL PROTECTED] wrote:
We have a table with a primary index which is INT NOT NULL
AUTO_INCREMENT.
After inserting ~87,000,000 entries, we started seeing error 1062,
ER_DUP_ENTRY.
We can get going again after doing an ALTER TABLE to reset the
Hi All,
Good day !!!
I'm using phpmyadmin to create database on Mysql server. I want my idx to
start at 1800 then implement auto increment. How do i do it using
phpmyadmin?
Regards,
Delz,
-
Before posting, please check:
I've written a C program which inserts new entries into a table
with an auto_incremented column. In testing it I created several entries,
which I then deleted by connecting to mysql from the unix command line.
The problem is, when I reset the last_insert_id from the mysql prompt, it
[EMAIL PROTECTED] wrote:
Your message cannot be posted because it appears to be either spam or
simply off topic to our filter. To bypass the filter you must include
one of the following words in your message:
sql,query
If you just reply to this message, and include the entire text of it in the
Hi,
I've continued trying to solve the problem that I emailed yesterday
regarding AUTO_INCREMENT, and I just seem to be going backwards.
The sample database/software that I sent yesterday had a UNIQUE
constraint and a couple of SELECT statements. I thought that removing
them bizarrely made
Hi, got a problem:
My table (part of it) looks like this:
CREATE TABLE cust (
id SMALLINT UNSIGNED NOT NULL AUTO_INCREMENT,
name CHAR(30) NOT NULL,
PRIMARY KEY (id)
);
When i type
INSERT INTO cust VALUES(NULL,Peter);
the value of id will increase by 1 every time i insert a record.
By misstake
At 4:47 PM +0200 7/25/01, Peter Wiherkoski wrote:
Hi, got a problem:
My table (part of it) looks like this:
CREATE TABLE cust (
id SMALLINT UNSIGNED NOT NULL AUTO_INCREMENT,
name CHAR(30) NOT NULL,
PRIMARY KEY (id)
);
When i type
INSERT INTO cust VALUES(NULL,Peter);
the value of id will
-webShop.com www.iConnect.de
# Gustav-Meyer-Allee 25, 13355 Berlin
# Tel: +49-30-46307-382 Fax: +49-30-46307-388
- Original Message -
From: Peter Wiherkoski [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, July 25, 2001 4:47 PM
Subject: AUTO_INCREMENT problem in table
Hi, got
: AUTO_INCREMENT problem in table
Dear Peter,
Even if i delete the record where id=65535
DELETE FROM cust WHERE id=65535
AUTO_INCREMENT starts with 65535 and i cant add any more records.
Sad, but true, MySQL remembers the biggest number inserted into an
auto_increment column. If you delete the row
Dear Peter,
Even if i delete the record where id=65535
DELETE FROM cust WHERE id=65535
AUTO_INCREMENT starts with 65535 and i cant add any more records.
Sad, but true, MySQL remembers the biggest number inserted into an
auto_increment column. If you delete the row in question, the
William R. Mussatto writes:
On Wed, 14 Feb 2001, Sinisa Milivojevic wrote:
can an auto_increment column also have the attribute "unsigned" safely?
Sincerely,
William Mussatto, Senior Systems Engineer
CyberStrategies, Inc
ph. 909-920-9154 ext. 27
Yes it can.
Regards,
with all of idle CPU
time used. if I tried to strace that mysqld process with strace -p ...,
it created a null length file and the process exists. However at home
with mysql 3.23.31 it was fine, and with 3.23.32 it's okey too, but now
I have got this auto_increment problem).
Note, that I USED id
with mysql 3.23.31 it was fine, and with 3.23.32 it's okey too, but now
I have got this auto_increment problem).
Note, that I USED id -1 in this table for a special purpose, but now I
deleted ALL ids smaller than 1 then I tried to insert but it does not
work. It didn't work if I tried to dump
On Wed, Feb 14, 2001 at 02:38:11PM +0200, Sinisa Milivojevic wrote:
Hi!
I have just tested your case on my Linux and it worked just fine.
What OS is that and are you using our binaries. If not, please do.
OK, I will (but it takes some time to download).
Till that I have got a more
Gbor Lnrt writes:
On Wed, Feb 14, 2001 at 02:38:11PM +0200, Sinisa Milivojevic wrote:
Hi!
I have just tested your case on my Linux and it worked just fine.
What OS is that and are you using our binaries. If not, please do.
OK, I will (but it takes some time to download).
On Wed, Feb 14, 2001 at 04:21:31PM +0200, Sinisa Milivojevic wrote:
Hi!
The above is actually documented behaviour.
I've just realized that it's true (checked). But it was supported by older
mysql versions and now I'm getting stuck with the old tables (MyISAM).
Entering negative values
On Wed, 14 Feb 2001, Sinisa Milivojevic wrote:
Date: Wed, 14 Feb 2001 16:21:31 +0200 (EET)
From: Sinisa Milivojevic [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: auto_increment problem with mysql 3.23.32
snip..
Hi!
The above is actually documented
38 matches
Mail list logo
