x schrieb:
thanks
may you point out which chapter says?
From manual I get the following answer agaist to my result(my server
version 5.0.45),
For |InnoDB| before version 5.0.3, |TRUNCATE TABLE| is mapped to
|DELETE|, so there is no difference. Starting with MySQL 5.0.3, fast
|TRUNCATE TABLE|
thanks
may you point out which chapter says?
From manual I get the following answer agaist to my result(my server
version 5.0.45),
For |InnoDB| before version 5.0.3, |TRUNCATE TABLE| is mapped to
|DELETE|, so there is no difference. Starting with MySQL 5.0.3, fast
|TRUNCATE TABLE| is availab
Martijn Tonies schrieb:
>
>>> [...] why in procedure TRUNCATE table
>>> demo do not reset auto_increment?
>> is clearly written in the documentation, just read ...
>>
>> in short:
>>
>> auto_increment is used for primary key, primary keys could be
>> referenced
> > [...] why in procedure TRUNCATE table
> > demo do not reset auto_increment?
> is clearly written in the documentation, just read ...
>
> in short:
>
> auto_increment is used for primary key, primary keys could be
> referenced
> from another table, se
Martijn Tonies schrieb:
> [...] why in procedure TRUNCATE table
> demo do not reset auto_increment?
is clearly written in the documentation, just read ...
in short:
auto_increment is used for primary key, primary keys could be
referenced
from another table
> >>> [...] why in procedure TRUNCATE table
> >>> demo do not reset auto_increment?
> >> is clearly written in the documentation, just read ...
> >>
> >> in short:
> >>
> >> auto_increment is used for primary key, primary keys could be
referenced
> >> from another table, setting auto_increment back
Martijn Tonies schrieb:
>>> [...] why in procedure TRUNCATE table
>>> demo do not reset auto_increment?
>> is clearly written in the documentation, just read ...
>>
>> in short:
>>
>> auto_increment is used for primary key, primary keys could be referenced
>> from another table, setting auto_increm
> > [...] why in procedure TRUNCATE table
> > demo do not reset auto_increment?
>
> is clearly written in the documentation, just read ...
>
> in short:
>
> auto_increment is used for primary key, primary keys could be referenced
> from another table, setting auto_increment back to 0 could lead to
过客 schrieb:
> [...] why in procedure TRUNCATE table
> demo do not reset auto_increment?
is clearly written in the documentation, just read ...
in short:
auto_increment is used for primary key, primary keys could be referenced
from another table, setting auto_increment back to 0 could lead to usi
*hi everyone: *
I've some puzzle with the following test:
CREATE TABLE `demo` (
`id` int(11) NOT NULL auto_increment,
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 ;
INSERT INTO demo VALUES(100);
delimiter //
create procedure test()
DETERMINISTIC
begin
10 matches
Mail list logo
