2013/3/13 Reindl Harald h.rei...@thelounge.net:
Am 12.03.2013 22:34, schrieb spameden:
NOTE: AUTO_INCREMENT is 32768 instead of 17923 ! So next inserted row
would have pc_id=32768.
Please suggest if it's normal behavior or not
what do you expect if a PRIMARY KEY record get's removed?
Furthermore I've tested on 133K records and AUTO_INCREMENT field in
the end had the value of 234076.
mysql select count(*) from billing.phone_codes;
+--+
| count(*) |
+--+
| 12 |
+--+
1 row in set (0.02 sec)
AUTO_INCREMENT=234076
So it basically means If I have
of those are covered here:
http://mysql.rjweb.org/doc.php/ricksrots
-Original Message-
From: spameden [mailto:spame...@gmail.com]
Sent: Tuesday, March 12, 2013 2:46 PM
To: Rick James
Cc: mysql@lists.mysql.com
Subject: Re: auto_increment field behavior
2013/3/13 Rick James rja
of those are covered here:
http://mysql.rjweb.org/doc.php/ricksrots
-Original Message-
From: spameden [mailto:spame...@gmail.com]
Sent: Tuesday, March 12, 2013 2:46 PM
To: Rick James
Cc: mysql@lists.mysql.com
Subject: Re: auto_increment field behavior
2013/3/13 Rick James rja
Subject: Re: auto_increment field behavior
2013/3/13 Rick James rja...@yahoo-inc.com:
What settings? (innodb_autoinc_lock_mode comes to mind, but there
may
be others.)
Hi, Rick.
Many thanks for the quick answer here is my settings:
mysql show variables like '%inc
What settings? (innodb_autoinc_lock_mode comes to mind, but there may be
others.)
It is acceptable, by the definition of AUTO_INCREMENT, for it to burn the
missing 15K ids.
-Original Message-
From: spameden [mailto:spame...@gmail.com]
Sent: Tuesday, March 12, 2013 2:34 PM
To:
2013/3/13 Rick James rja...@yahoo-inc.com:
What settings? (innodb_autoinc_lock_mode comes to mind, but there may be
others.)
Hi, Rick.
Many thanks for the quick answer here is my settings:
mysql show variables like '%inc%';
+-+---+
| Variable_name
To: Rick James
Cc: mysql@lists.mysql.com
Subject: Re: auto_increment field behavior
2013/3/13 Rick James rja...@yahoo-inc.com:
What settings? (innodb_autoinc_lock_mode comes to mind, but there
may
be others.)
Hi, Rick.
Many thanks for the quick answer here is my settings:
mysql show
of those are covered here:
http://mysql.rjweb.org/doc.php/ricksrots
-Original Message-
From: spameden [mailto:spame...@gmail.com]
Sent: Tuesday, March 12, 2013 2:46 PM
To: Rick James
Cc: mysql@lists.mysql.com
Subject: Re: auto_increment field behavior
2013/3/13 Rick James rja
Am 12.03.2013 22:34, schrieb spameden:
NOTE: AUTO_INCREMENT is 32768 instead of 17923 ! So next inserted row
would have pc_id=32768.
Please suggest if it's normal behavior or not
what do you expect if a PRIMARY KEY record get's removed?
re-use the same primary key?
this is not the way a
- Original Message -
From: crocket crockabisc...@gmail.com
I had 19 rows in series table. And when I tried inserting the 20th
row, the auto_increment value suddenly increased from 20 to 32, and
the new row has 20 as series_id.
The first thing that comes to mind, is transactions that
Den 23-02-2011 18:41, Jim McNeely skrev:
Is there a way to set the auto-increment for a particular table to increase by
some number more than one, like maybe 10?
Thanks in advance,
Jim McNeely
CREATE TABLE t (
...
) AUTO_INCREMENT=10;
/ Carsten
--
MySQL General Mailing List
For list
On 2/23/2011 12:41, Jim McNeely wrote:
Is there a way to set the auto-increment for a particular table to increase by
some number more than one, like maybe 10?
Thanks in advance,
Jim McNeely
The manual is your friend. Don't be afraid of it :)
I have read the manual, and you're right, the auto-increment_increment is a
system wide setting. I only want this on one table. I am in this instance
creating ID's for a separate system via HL7 for a Filemaker system, and
FileMaker is too lame and slow to actually spit out an ID in time for the
This doesn't work, it just sets the starting number, but it will still
increment by one unless you set the auto_increment_increment system variable,
but this affects all the tables in the DB and not just the particular table.
Thanks,
Jim McNeely
On Feb 23, 2011, at 10:26 AM, Carsten Pedersen
Am 23.02.2011 22:29, schrieb Jim McNeely:
I have read the manual, and you're right, the auto-increment_increment is a
system wide setting
No, scope session means set VAR=value
Command-Line Format --auto_increment_increment[=#]
Option-File Format auto_increment_increment
Option Sets
Am 23.02.2011 22:55, schrieb Singer X.J. Wang:
Yes, you can set it up so that it increases it by X only for that statement..
eg.
[other stuff]
set auto_increment_increment = X;
insert into that table you want
set auto_increment_increment = 1;
[other stuff]
Now you have to remmeber
what is the value u see when you execute
select max(b) from y;
On Thu, Feb 18, 2010 at 1:33 PM, Gavin Towey gto...@ffn.com wrote:
Reproduced in 5.1.43. Could not reproduce it in 5.0.66
-Original Message-
From: Yang Zhang [mailto:yanghates...@gmail.com]
Sent: Wednesday, February
Reproduced in 5.1.43. Could not reproduce it in 5.0.66
-Original Message-
From: Yang Zhang [mailto:yanghates...@gmail.com]
Sent: Wednesday, February 17, 2010 6:05 PM
To: mysql@lists.mysql.com
Subject: auto_increment weirdness
Hi, for some reason, I have an auto_increment field that's
On Mon, Jan 25, 2010 at 10:08 PM, Yong Lee yong@gogoants.com wrote:
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 :
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
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));
Date: Fri, 10 Apr 2009 15:15:28 +0530
From: jnaneshwar.banta...@kavach.net
To: mysql@lists.mysql.com
Subject: auto_increment Issue
Hi All
I have created a table.Now I need to make a field Auto_increment...Help
me with this issue..An example will do..
Regards
Jnani
Hi Jnani,
- Original Message - From: abdulazeez alugo
defati...@hotmail.com
To: jnaneshwar.banta...@kavach.net; mysql@lists.mysql.com
Sent: Friday, April 10, 2009 1:07 PM
Subject: RE: auto_increment Issue
Date: Fri, 10 Apr 2009 15:15:28 +0530
From: jnaneshwar.banta...@kavach.net
Date: Fri, 10 Apr 2009 15:55:33 +0530
From: jnaneshwar.banta...@kavach.net
To: orasn...@gmail.com
CC: defati...@hotmail.com; mysql@lists.mysql.com
Subject: Re: auto_increment Issue
Hi
While trying for the same,I am getting the following error
Incorrect table definition
Hi ,
Thanks,Its working now
Jnani
abdulazeez alugo wrote:
Date: Fri, 10 Apr 2009 15:55:33 +0530
From: jnaneshwar.banta...@kavach.net
To: orasn...@gmail.com
CC: defati...@hotmail.com; mysql@lists.mysql.com
Subject: Re: auto_increment Issue
Hi
While trying for the same,I am
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
Hiep Nguyen schrieb:
hi list,
reading manual on mysql regarding auto_increment with multiple-column
index:
CREATE TABLE animals (
grp ENUM('fish','mammal','bird') NOT NULL,
id MEDIUMINT NOT NULL AUTO_INCREMENT,
name CHAR(30) NOT NULL,
PRIMARY KEY (grp,id)
);
INSERT INTO
Sebastian Mendel schrieb:
Hiep Nguyen schrieb:
hi list,
reading manual on mysql regarding auto_increment with multiple-column
index:
CREATE TABLE animals (
grp ENUM('fish','mammal','bird') NOT NULL,
id MEDIUMINT NOT NULL AUTO_INCREMENT,
name CHAR(30) NOT NULL,
PRIMARY KEY
Are you sure, I just get:
CREATE TABLE ...
ERROR 1075 (42000): Incorrect table definition; there can be only one
auto column and it must be defined as a key
On version 5.0.41. What version are you using?
Hiep Nguyen wrote:
hi list,
reading manual on mysql regarding auto_increment with
Ben Clewett schrieb:
Are you sure, I just get:
CREATE TABLE ...
ERROR 1075 (42000): Incorrect table definition; there can be only one
auto column and it must be defined as a key
the mentioned CREATE TABLE is fine and works
On version 5.0.41. What version are you using?
this works on
You are right, I've tried 5.0.18 and 5.0.45 which work.
There must have been a bug in 5.0.41 with which I used test the question...
I belive the question has been answered by now anyway :)
Ben
Sebastian Mendel wrote:
Ben Clewett schrieb:
Are you sure, I just get:
CREATE TABLE ...
ERROR
On Tue, 22 Apr 2008, Sebastian Mendel wrote:
Sebastian Mendel schrieb:
Hiep Nguyen schrieb:
hi list,
reading manual on mysql regarding auto_increment with multiple-column
index:
CREATE TABLE animals (
grp ENUM('fish','mammal','bird') NOT NULL,
id MEDIUMINT NOT NULL AUTO_INCREMENT,
David - there's some info in the online docs here:
http://dev.mysql.com/doc/refman/5.0/en/example-auto-increment.html
Specifically:
To start with an AUTO_INCREMENT value other than 1, you can set that
value with CREATE TABLE or ALTER TABLE, like this:
mysql ALTER TABLE tbl AUTO_INCREMENT = 100;
Thanks, Dan, but I can't get it to work. Defining a column like this:
a int not null auto_increment=0 primary key
throws an error, and while the alter table statement seems to work ok,
whether the table is empty or not, it has no effect on subsequent inserts.
I'm wondering if 4.0.16 has not
OK. If you assign to auto_increment any number higher than what currently
exists in the column, it changes the value and the incremented sequence
from that point. But apparently you can't assign the value zero to the
column, even if the table is empty.
Thanks, Dan, but I can't get it to work.
I just tried it in 5.0.21, and found that it fails silently with zero
(0). Works with 100. I did specify int, not unsigned int, in my test
table.
See http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html
for some discussion about how you could get a zero in there; look for
At 14:16 -0500 9/22/06, [EMAIL PROTECTED] wrote:
I seem to recall that when creating a table, you could designate an
auto_increment field to begin counting at zero(0) instead of one (1), but I
can't find an example in the documents.
Don't store 0 in an AUTO_INCREMENT column.
--
Paul DuBois,
At 14:16 -0500 9/22/06, [EMAIL PROTECTED] wrote:
I seem to recall that when creating a table, you could designate an
auto_increment field to begin counting at zero(0) instead of one (1),
but I
can't find an example in the documents.
Don't store 0 in an AUTO_INCREMENT column.
Thanks Dan
Hi Mark
People_id is the column with auto increment? You can verify that it
really does have auto_increment by using the describe command. For
example:
mysql describe checks;
+-+--+--+-+-
++
| Field | Type
At 19:12 +1000 6/1/06, Mark Sargent wrote:
Hi All,
if a table has an auto_incremented primary key why does the below
code require the people_id to be manually inserted? I got this from
Beginning PHP, Apache, MySQL Web Development book from Wrox.
Curious, as it seems to defeat the purpose of
Stanton, Brian wrote:
I'm migrating a database from 4.0.12 on Solaris to 4.0.18-0 on Red Hat
Linux. A few of the tables have a 0 (zero) in the auto_increment primary
key column. However, when importing, the 0 in the insert is translated to
the next available auto_increment value thus causing a
[EMAIL PROTECTED]
Subject: Re: auto_increment and the value 0
Stanton, Brian wrote:
I'm migrating a database from 4.0.12 on Solaris to 4.0.18-0 on Red
Hat
Linux. A few of the tables have a 0 (zero) in the auto_increment
primary
key column. However, when importing, the 0 in the insert
[EMAIL PROTECTED] wrote:
Are you saying just change the row with the 0 value as the
PK, and change the FK's in the related tables to point to
the new value instaed of 0?
Yes.
If so, would this move the row logically to the end of the
table, if the 0 PK was replaced with the next
On 30/03/2006 12:31 p.m., Daniel Kasak wrote:
[EMAIL PROTECTED] wrote:
I suppose that would be alot easier than trying to bump the PK and
related FK values of the whole table by 1, just to give the first row
in the table the auto_increment value of 1?
Yes. That sounds messy.
What about
You can override MySQL behaviour of generating a new value if you insert a 0
into an auton_increment field.
Quoting from the manual:
NO_AUTO_VALUE_ON_ZERO affects handling of AUTO_INCREMENT columns.
Normally, you generate the next sequence number for the column by inserting
either NULL or 0
On 24/03/2006 11:06 a.m., Eric Beversluis wrote:
Can someone illustrate the correct syntax for using auto_increment in
making a table? I've studied the manual and I'm not seeing how it comes
out.
EG:
CREATE TABLE Books (
bookID INT(5) PRIMARY KEY AUTO_INCREMENT...
THEN WHAT?
Thanks.
EB
Hello.
Please, could add more details of your actions. Are you inserting in the
table which already has data? Please, provide exact error message. I'm
not a telepathist, but in case of duplicate key errors a brute solution
is to perform a dump with --insert-ignore option.
Scott Johnson wrote:
You can change the table definition to not have the auto_increment
column, and then ALTER TABLE MODIFY COLUMN after that. However, if
you post your errors here, perhaps you'll get the answer that actually
solves the problem, instead of working around it to possibly leave bad
data for you to
http://dev.mysql.com/doc/refman/4.1/en/odbc-and-last-insert-id.html
|
| Cal Evans
| http://www.calevans.com
|
Danesh Daroui wrote:
Hi all,
I have a simple table with an Auto_Increment column. I insert NULL
to this column each time I insert a row to have an automatic unique
value.
On 5/16/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,
with a similar structure, you can have :
mysql select * from users where uid =262140;
++--+
| uid| nickname |
++--+
| 262140 | text |
| 262141 | text |
| 262142 | text |
| 262143 |
This may not be a very elegant solution, but you can do this just to get the
inserts going again:
ALTER TABLE users
MODIFY COLUMN uid INTEGER UNSIGNED NOT NULL AUTO_INCREMENT;
If you don't have any negative uids, then you will be able to store 2
billion more uids.
Just out of curiosity, have
Partha,
On 5/16/05, Partha Dutta [EMAIL PROTECTED] wrote:
This may not be a very elegant solution, but you can do this just to get the
inserts going again:
ALTER TABLE users
MODIFY COLUMN uid INTEGER UNSIGNED NOT NULL AUTO_INCREMENT;
If you don't have any negative uids, then you will be
Hi,
with a similar structure, you can have :
mysql select * from users where uid =262140;
++--+
| uid| nickname |
++--+
| 262140 | text |
| 262141 | text |
| 262142 | text |
| 262143 | text |
| 262144 | text |
++--+
5 rows in
Partha,
Partha Dutta wrote:
This may not be a very elegant solution, but you can do this just to get the
inserts going again:
ALTER TABLE users
MODIFY COLUMN uid INTEGER UNSIGNED NOT NULL AUTO_INCREMENT;
If you don't have any negative uids, then you will be able to store 2
billion more uids.
Just
Jim McAtee wrote:
Say a row is inserted into a table with an auto_increment column and
then deleted before another record is inserted. When a new row is
inserted, will the value of the auto_increment column be the same as
the deleted record's, or will it be one greater?
Greater.
--
Daniel
Jim McAtee [EMAIL PROTECTED] wrote on 02/24/2005 04:50:11 PM:
Say a row is inserted into a table with an auto_increment column and
then
deleted before another record is inserted. When a new row is inserted,
will the value of the auto_increment column be the same as the deleted
record's,
I am not really experienced on this, but i have noticed that simply
truncating an innodb table doesnt reset the autoinc key, u have to redump
the table.
I cant see what you are trying to do here
ALTER TABLE users auto_increment = 590;
set it to start @ 590 ?
Hello,
I am trying to get
it doesn't work with innodb table.
http://dev.mysql.com/doc/mysql/en/innodb-restrictions.html
InnoDB does not support the AUTO_INCREMENT table option for setting the
initial sequence value in a CREATE TABLE or ALTER TABLE statement. To set
the value with InnoDB, insert a dummy row with a value
Hello.
Use the NO_AUTO_VALUE_ON_ZERO sql mode. See:
http://dev.mysql.com/doc/mysql/en/server-sql-mode.html
Philippe Rousselot [EMAIL PROTECTED] wrote:
hi,
I am migrating a DB having a table with a UID not_null autoincrement
the original table starts at UID=0
I
Hello.
There were several bugs in older versions of MySQL related to 'duplicate entry'
errors. Do you use latest release? In documentation it is said that
AUTO_INCREMENT
works correctly with replication. Please also take a look in the documentation
at these links:
According to http://dev.mysql.com/doc/mysql/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.
It did not specify that the AUTO_INCREMENT column couldn't have a regular
index on it.
If you have this table:
I hate to dampen your spirits but I think you have made a poor design
choice.
BEGIN GLOOM and DOOM
The word key is a reserved word in MySQL. In order to assign to a
database object a name that is either a reserved word or a name that uses
a special character, you must surround that with a
If you do an
ALTER TABLE table_name MODIFY id INTEGER AUTO_INCREMENT, ADD PRIMARY
KEY(id);
...
The next record entered should be properly auto_incremented.
-Original Message-
From: Scott Hamm
To: 'Mysql ' (E-mail)
Sent: 8/11/04 1:32 PM
Subject: Auto_increment and existing table
I've
Thanks!
-Original Message-
From: Victor Pendleton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 11, 2004 3:40 PM
To: 'Scott Hamm '; ''Mysql ' (E-mail) '
Subject: RE: Auto_increment and existing table
If you do an
ALTER TABLE table_name MODIFY id INTEGER AUTO_INCREMENT, ADD PRIMARY
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
On Jun 18, 2004, at 5:31 PM, Scott Haneda wrote:
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.
While I do not know why, I
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
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
I found the answer to my question by reading the online manual with user
comments.
Sorry!.
Mark
- Original Message -
From: Mark Fuller [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, May 09, 2004 12:25 AM
Subject: auto_increment question
I would like to use MEDIUMINT UNSIGNED
Stefan Schuster [EMAIL PROTECTED] wrote:
Stefan Schuster [EMAIL PROTECTED] wrote:
Hi,
I have a question about auto_increment:
I have 2 tables, on of them holds my online transactions, the other
one the offline transactions. Every transaction is created in the
first table (call it t1) and
PROTECTED]
Sent: Friday, March 12, 2004 9:35 AM
Subject: Re: auto_increment id
Stefan Schuster [EMAIL PROTECTED] wrote:
Stefan Schuster [EMAIL PROTECTED] wrote:
Hi,
I have a question about auto_increment:
I have 2 tables, on of them holds my online transactions, the other
one
Stefan Schuster [EMAIL PROTECTED] wrote:
Hi,
I have a question about auto_increment:
I have 2 tables, on of them holds my online transactions, the other
one the offline transactions. Every transaction is created in the
first table (call it t1) and then moved to t2. The id is generated
Stefan Schuster [EMAIL PROTECTED] wrote:
Hi,
I have a question about auto_increment:
I have 2 tables, on of them holds my online transactions, the other
one the offline transactions. Every transaction is created in the
first table (call it t1) and then moved to t2. The id is generated
When you create the table I think you just set it..
ie- create table blah AUTO_INCREMENT=
P
-Scott Purcell [EMAIL PROTECTED] wrote: -
To: [EMAIL PROTECTED]
From: Scott Purcell [EMAIL PROTECTED]
Date: 02/09/2004 12:21PM
Subject: auto_increment pseudo sequence?
Hello,
I have
alter table AUTO_INCREMENT=x
Scott Purcell wrote:
Hello,
I have an application in which I am using auto_increment as a kind of sequence replacement. The only problem I have is trying to get the auto_increment to start at a larger number than 0.
Is auto_increment the replacement for sequences?
Hassan,
- Original Message -
From: Hassan Shaikh [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Sunday, February 01, 2004 5:01 PM
Subject: AUTO_INCREMENT in InnoDB
Hi,
How do I reset the AUTO_INCREMENT column to some arbitrary number? My
table type is InnoDB.
* Chris W
I have two tables with a one to many relationship: boys and their toys.
I want to know if there are any advantages or disadvantages for each
of the following two ways to create the tables. I am mainly interested
in performance. Either way the insert and select queries aren't any
Dan Muey [EMAIL PROTECTED] wrote:
I have a table that I create with=20
CREATE TABLE SuperTest (
ID int(11) NOT NULL AUTO_INCREMENT,
Name varchar(64) NOT NULL,
Domain varchar(64) NOT NULL,
PRIMARY KEY(ID)
);
I use that same thing to create a the same table
Dan Muey [EMAIL PROTECTED] wrote:
I have a table that I create with=20
CREATE TABLE SuperTest (
ID int(11) NOT NULL AUTO_INCREMENT,
Name varchar(64) NOT NULL,
Domain varchar(64) NOT NULL,
PRIMARY KEY(ID)
);
I use that same thing to create a
Dan Muey [EMAIL PROTECTED] wrote:
Dan Muey [EMAIL PROTECTED] wrote:
I have a table that I create with=3D20
CREATE TABLE SuperTest (
ID int(11) NOT NULL AUTO_INCREMENT,
Name varchar(64) NOT NULL,
Domain varchar(64) NOT NULL,
PRIMARY KEY(ID)
);
I use
Dan Muey [EMAIL PROTECTED] wrote:
Dan Muey [EMAIL PROTECTED] wrote:
I have a table that I create with=3D20
CREATE TABLE SuperTest (
ID int(11) NOT NULL AUTO_INCREMENT,
Name varchar(64) NOT NULL,
Domain varchar(64) NOT NULL,
PRIMARY KEY(ID)
);
vinita vigine MURUGIAH [EMAIL PROTECTED] wrote:
Hello,
I'm using ver 4.0.12, checked for bugs in ver
4.0.12(http://bugs.mysql.com/search.php) but couldn't find this one.
Thanks for report, but I wasn't able to repeat Lost connection error on v4.0.16.
Many bugs were fixed since that time.
Vinita,
it is most probably this bug fixed in 4.1.14:
Fixed a bug: if in a FOREIGN KEY with an UPDATE CASCADE clause the parent
column was of a different internal storage length than the child column,
then a cascaded update would make the column length wrong in the child table
and corrupt the
On Wed, 27 Aug 2003 09:05:17 -0300
bernardaum [EMAIL PROTECTED] wrote:
Hi,
I have a table with an auto_increment field. When I
delete all the record and insert a new one the
auto_increment field is not clean, its follows the
sequence.
Can I restart this sequence? Start from 0 again?
On Wednesday 27 August 2003 1:05 pm, bernardaum wrote:
Hi,
I have a table with an auto_increment field. When I
delete all the record and insert a new one the
auto_increment field is not clean, its follows the
sequence.
Can I restart this sequence? Start from 0 again?
When I need to do
On Wed, 27 Aug 2003 13:27:25 +0100
Simon [EMAIL PROTECTED] wrote:
On Wednesday 27 August 2003 1:05 pm, bernardaum wrote:
Hi,
I have a table with an auto_increment field. When I
delete all the record and insert a new one the
auto_increment field is not clean, its follows the
sequence.
At 9:05 -0300 8/27/03, bernardaum wrote:
Hi,
I have a table with an auto_increment field. When I
delete all the record and insert a new one the
auto_increment field is not clean, its follows the
sequence.
Can I restart this sequence? Start from 0 again?
Why bother? MySQL doesn't care if there
On Wed, 27 Aug 2003 09:38:16 -0400
Paul DuBois [EMAIL PROTECTED] wrote:
At 9:05 -0300 8/27/03, bernardaum wrote:
Hi,
I have a table with an auto_increment field. When I
delete all the record and insert a new one the
auto_increment field is not clean, its follows the
sequence.
Can I
1 - 100 of 244 matches
Mail list logo
