30 Jul
2006
30 Jul
'06
9 a.m.
Hi,
starting with MySQL 5.0.23, SHOW CREATE TABLE includes the
AUTO_INCREMENT next value, just after the ENGINE clause.
We had a "Add AUTO_INCREMENT value" option in table operations and db
operations.
So I suggest:
- for 5.0.23+, the "Add AUTO_INCREMENT value" checkbox be removed from
table operations and db operations dialogs. The same functionality is
now being provided automatically in the CREATE TABLE statement
- for 5.0.22-, I would also prefer to remove these checkboxes
For all MySQL versions, I guess that during a copy, the majority of
users want to copy also the AUTO_INCREMENT value. If it's not the case,
they can always go to the copied table on Operations and change the
value in "Table options".
If we still want to provide this checkbox, well for 5.0.23+ we would
have to examine the statement and remove the AUTO_INCREMENT clause.
Marc
31 Jul
31 Jul
11:10 a.m.
Hi Marc and others
On Sun, 30 Jul 2006 08:00:03 -0400
Marc Delisle <Marc.Delisle(a)cegepsherbrooke.qc.ca> wrote:
starting with MySQL 5.0.23, SHOW CREATE TABLE includes
the
AUTO_INCREMENT next value, just after the ENGINE clause.
We had a "Add AUTO_INCREMENT value" option in table operations and db
operations.
So I suggest:
- for 5.0.23+, the "Add AUTO_INCREMENT value" checkbox be removed from
table operations and db operations dialogs. The same functionality is
now being provided automatically in the CREATE TABLE statement
- for 5.0.22-, I would also prefer to remove these checkboxes
For all MySQL versions, I guess that during a copy, the majority of
users want to copy also the AUTO_INCREMENT value. If it's not the case,
they can always go to the copied table on Operations and change the
value in "Table options".
If we still want to provide this checkbox, well for 5.0.23+ we would
have to examine the statement and remove the AUTO_INCREMENT clause.
The problem is that we reuse the code from export and there we probably
want checkbox for AUTO_INCREMENT...
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
11:35 a.m.
Michal Čihař a écrit :
Hi Marc and others
On Sun, 30 Jul 2006 08:00:03 -0400
Marc Delisle <Marc.Delisle(a)cegepsherbrooke.qc.ca> wrote:
You mean, even if MySQL 5.0.23+ now already adds AUTO_INCREMENT? So you
see a situation in export where a user would not want to AUTO_INCREMENT
next value?
Marc
starting with MySQL 5.0.23, SHOW CREATE TABLE
includes the
AUTO_INCREMENT next value, just after the ENGINE clause.
We had a "Add AUTO_INCREMENT value" option in table operations and db
operations.
So I suggest:
- for 5.0.23+, the "Add AUTO_INCREMENT value" checkbox be removed from
table operations and db operations dialogs. The same functionality is
now being provided automatically in the CREATE TABLE statement
- for 5.0.22-, I would also prefer to remove these checkboxes
For all MySQL versions, I guess that during a copy, the majority of
users want to copy also the AUTO_INCREMENT value. If it's not the case,
they can always go to the copied table on Operations and change the
value in "Table options".
If we still want to provide this checkbox, well for 5.0.23+ we would
have to examine the statement and remove the AUTO_INCREMENT clause.
The problem is that we reuse the code from export and there we probably
want checkbox for AUTO_INCREMENT...
11:47 a.m.
Marc Delisle a écrit :
Michal Čihař a écrit :
Rephrased:
So you see a situation in export where a user would not want to see the
AUTO_INCREMENT next value in the exported file?
Marc
Hi Marc and others
On Sun, 30 Jul 2006 08:00:03 -0400
Marc Delisle <Marc.Delisle(a)cegepsherbrooke.qc.ca> wrote:
You mean, even if MySQL 5.0.23+ now already adds AUTO_INCREMENT? So you
see a situation in export where a user would not want to AUTO_INCREMENT
next value? starting with MySQL 5.0.23, SHOW CREATE TABLE
includes the
AUTO_INCREMENT next value, just after the ENGINE clause.
We had a "Add AUTO_INCREMENT value" option in table operations and db
operations.
So I suggest:
- for 5.0.23+, the "Add AUTO_INCREMENT value" checkbox be removed from
table operations and db operations dialogs. The same functionality is
now being provided automatically in the CREATE TABLE statement
- for 5.0.22-, I would also prefer to remove these checkboxes
For all MySQL versions, I guess that during a copy, the majority of
users want to copy also the AUTO_INCREMENT value. If it's not the case,
they can always go to the copied table on Operations and change the
value in "Table options".
If we still want to provide this checkbox, well for 5.0.23+ we would
have to examine the statement and remove the AUTO_INCREMENT clause.
The problem is
that we reuse the code from export and there we probably
want checkbox for AUTO_INCREMENT...
1 Aug
1 Aug
5:39 a.m.
On Mon, 31 Jul 2006 10:47:29 -0400
Marc Delisle <Marc.Delisle(a)cegepsherbrooke.qc.ca> wrote:
So you see a situation in export where a user would
not want to see the
AUTO_INCREMENT next value in the exported file?
Well it would be useful not to export auto incremented column at all,
but will full export there won't be much use for it...
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
12:20 p.m.
Michal Čihař a écrit :
On Mon, 31 Jul 2006 10:47:29 -0400
Marc Delisle <Marc.Delisle(a)cegepsherbrooke.qc.ca> wrote:
Ok I'll try to implement the removal of AUTO_INCREMENT clause generated
by 5.0.23+ SHOW CREATE TABLE.
So you see a situation in export where a user
would not want to see the
AUTO_INCREMENT next value in the exported file?
Well it would be useful not to export auto incremented column at all, but will full export there won't be much use for
it...
Sorry I don't follow your point about full export.
Marc
2 Aug
2 Aug
7:28 a.m.
On Tue, 01 Aug 2006 11:20:19 -0400
Marc Delisle <Marc.Delisle(a)cegepsherbrooke.qc.ca> wrote:
Michal Čihař a écrit :
Sorry for mess, I will try to rephrase this:
When you export table with all columns, you will most likely want
AUTO_INCREMENT to be included.
However if we'd provide option to export table without auto incremented
column, not exporting AUTO_INCREMENT would be logical.
So I think that it's okay to have AUTO_INCREMENT clause.
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
On Mon, 31 Jul 2006 10:47:29 -0400
Marc Delisle <Marc.Delisle(a)cegepsherbrooke.qc.ca> wrote:
Ok I'll try to implement the removal of AUTO_INCREMENT clause generated
by 5.0.23+ SHOW CREATE TABLE.
So you see a situation in export where a user
would not want to see the
AUTO_INCREMENT next value in the exported file?
Well it would be useful not to export auto incremented column at all, but will full export there won't be much use
for it...
Sorry I don't follow your point about full export. 
8:40 a.m.
hi devels,
When you export table with all columns, you will most
likely want
AUTO_INCREMENT to be included.
it depends on what your goal is -
if you want to copy structure & data you are right,
but if you want to setup an empty db
you probably want AUTO_INCREMENT value not to be set.
so in "table ->operation->copy" the checkbox should stay
and should be checked by default, as "Structure and data" is also
checked by default (same in "Move table to").
IMHO
--
View this message in context:
http://www.nabble.com/AUTO_INCREMENT-next-value-and-MySQL-5.0.23%2B-tf20231…
Sent from the phpmyadmin-devel forum at Nabble.com.
4 Aug
4 Aug
9:26 a.m.
windkiel a écrit :
hi devels,
Ok I'm convinced now :)
When you export table with all columns, you will
most likely want
AUTO_INCREMENT to be included.
it depends on what your goal is -
if you want to copy structure & data you are right,
but if you want to setup an empty db
you probably want AUTO_INCREMENT value not to be set.
so in "table ->operation->copy" the checkbox should stay
and should be checked by default, as "Structure and data" is also
checked by default (same in "Move table to").
IMHO
9:25 a.m.
Michal Čihař a écrit :
On Tue, 01 Aug 2006 11:20:19 -0400
Marc Delisle <Marc.Delisle(a)cegepsherbrooke.qc.ca> wrote:
OK I am working on this. 5.0.24 has been released but not yet on the
mirrors.
Michal Čihař a écrit :
Sorry for mess, I will try to rephrase this:
When you export table with all columns, you will most likely want
AUTO_INCREMENT to be included.
However if we'd provide option to export table without auto incremented
column, not exporting AUTO_INCREMENT would be logical.
So I think that it's okay to have AUTO_INCREMENT clause. On Mon, 31 Jul 2006 10:47:29 -0400
Marc Delisle <Marc.Delisle(a)cegepsherbrooke.qc.ca> wrote:
Ok I'll try to implement the removal of
AUTO_INCREMENT clause generated
by 5.0.23+ SHOW CREATE TABLE.
So you see a situation in export where a user
would not want to see the
AUTO_INCREMENT next value in the exported file?
Well it would be useful not to
export auto incremented column at all, but will full export there won't be much use
for it...
Sorry I don't follow your point about full export.
31 Jul
31 Jul
1:36 p.m.
Michal Čihař a écrit :
Hi Marc and others
On Sun, 30 Jul 2006 08:00:03 -0400
Marc Delisle <Marc.Delisle(a)cegepsherbrooke.qc.ca> wrote:
I just checked in the (not released) 5.0.25 and mysqldump always export
with this AUTO_INCREMENT clause. AFAIK we cannot avoid it in mysqldump.
Marc
starting with MySQL 5.0.23, SHOW CREATE TABLE
includes the
AUTO_INCREMENT next value, just after the ENGINE clause.
We had a "Add AUTO_INCREMENT value" option in table operations and db
operations.
So I suggest:
- for 5.0.23+, the "Add AUTO_INCREMENT value" checkbox be removed from
table operations and db operations dialogs. The same functionality is
now being provided automatically in the CREATE TABLE statement
- for 5.0.22-, I would also prefer to remove these checkboxes
For all MySQL versions, I guess that during a copy, the majority of
users want to copy also the AUTO_INCREMENT value. If it's not the case,
they can always go to the copied table on Operations and change the
value in "Table options".
If we still want to provide this checkbox, well for 5.0.23+ we would
have to examine the statement and remove the AUTO_INCREMENT clause.
The problem is that we reuse the code from export and there we probably
want checkbox for AUTO_INCREMENT...
6609
days inactive
6614
days old
10 comments
3 participants
participants (3)
-
Marc Delisle -
Michal Čihař -
windkiel