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
Martijn Tonies schrieb:
>
>>>>>>> [...] why in procedure TRUNCATE table
>>>>>>> demo do not reset auto_increment?
>>>>>> is clearly written in the documentation, just read ...
>>>>>>
>>>>>> in s
> >>>>> [...] why in procedure TRUNCATE table
> >>>>> demo do not reset auto_increment?
> >>>> is clearly written in the documentation, just read ...
> >>>>
> >>>> in short:
> >>>>
> >>>
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_
> >>> [...] 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 key
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 co
> > [...] 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 au
过客 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 l
begin
TRUNCATE table demo;
show table status like 'demo';
END//
delimiter ;
when call test() I got auto_increment=101, why in procedure TRUNCATE table
demo do not reset auto_increment?
any help much appreciate !
Sekhar,
- Original Message -
From: ""Sekhar.Thota"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Tuesday, December 03, 2002 3:14 PM
Subject: truncate table ...
> Dear All,
>
> I am getting a severe problem with truncate comand( InnoDB
Dear All,
I am getting a severe problem with truncate comand( InnoDB Tables
-
Mysql 3.23.52-MAX on Linux 7.3) .
The scenario is:
I have a table with more than 100 Million records. I gave a
truncate table command to delete all the data from this table. Once
I gave
tings,
Benjamin.
On Sat 2002-07-27 at 20:53:45 +0300, [EMAIL PROTECTED] wrote:
>
> BP> Hi.
>
> BP> First, when you start an independend question, please start a new
> BP> thread, but at least change the subject accordingly.
> This is not independent question. Man
Hello Benjamin,
BP> Hi.
BP> First, when you start an independend question, please start a new
BP> thread, but at least change the subject accordingly.
This is not independent question. Manual say what TRUNCATE TABLE will
recreate table from frm file, but when i use TRUNCATE TABLE, i
Hello Benjamin,
>> Why after TRUNCATE TABLE data file with indexes not freed ?
BP> See http://www.mysql.com/doc/A/d/Adding_and_removing.html (2nd paragraph)
BP> and
http://www.mysql.com/documentation/mysql/bychapter/manual_Table_types.html#InnoDB_File_space
BP> (second link d
Hi.
First, when you start an independend question, please start a new
thread, but at least change the subject accordingly.
On Fri 2002-07-26 at 11:07:17 +0300, [EMAIL PROTECTED] wrote:
[...]
> If table recreated from table.frm why it not recreate indexes file?
Because this is the documented beh
Hi.
On Fri 2002-07-26 at 11:03:26 +0300, [EMAIL PROTECTED] wrote:
> Hello Benjamin,
>
> >> Why after TRUNCATE TABLE data file with indexes not freed ?
> BP> See http://www.mysql.com/doc/A/d/Adding_and_removing.html (2nd paragraph)
> BP> and
>http://www.mysql.com
Hello mysql,
Why after TRUNCATE TABLE data file with indexes not freed ?
and TRUNCATE TABLE is very slow ...
MySQL 3.23.51+InnoDB
OS: Linux 2.4.18/ReiserFS
Best regards,
Andrew Sitnikov
e-mail : [EMAIL PROTECTED]
GSM: (+372) 56491109
Anti-SPAM: mysql, query
Gurus
I'm new to replication. Set it up this weekend and has worked
flawlessly for several days. Then I used the command:
TRUNCATE TABLE tbl;
That worked in master, but was not replicated in slave.
No mention of this in manual. Using version 3.23.49 on
maste
19 matches
Mail list logo
