Help - Search - Members - Calendar
Full Version: Has Delete Table Data Option Been Removed?
Webyog Forums > SQLyog > SQLyog Comments
malik
I recall testing with version 6.05 and it was possible to delete table data. I think it was in right click on the table adn there was an option there

I am testing with a later version - 6.16 - and this option is not available. You can only drop the whole table not just the data.

Is this correct?. They removed this option in the later versions?

I am testing with 6.16 community edition.

peterlaursen
It was renamed from 'empty table' to 'truncate table'. 'truncate table' is the correct SQL term.

Did I understand correctly?
malik
QUOTE (peterlaursen @ Apr 10 2008, 03:50 AM) *
It was renamed from 'empty table' to 'truncate table'. 'truncate table' is the correct SQL term.

Did I understand correctly?


Ahh i see, thank you Peter. The word 'Truncate' has a different meaning to me so i didn't consider it.

One other question if i may. I note there is now a character set on the import box. The default being utf8

The database i am looking at is showing as latin1

ENGINE=MyISAM DEFAULT CHARSET=latin1

No idea why this has latin1. This must be the default in Mysql when it was created. As far as i am aware there is no problem with leaving Yog set as utf8.
peterlaursen
Are you referring to CSV import?

Please refer to changelogs for version 6.16.

"-- Added an option to specify CHARSET parameter for CSV-import. Unicode (UTF8 and UCS2/UTF16) will be detected automatically. For files encoded with a non-unicode encoding, user must select the MySQL charset used for the import. Alternatively there is a <default> option that will not use the CHARSET parameter at all (= old program behavior)."

and to understand that client character set and server character may be different read

http://webyog.com/faq/content/34/102/en/wh...-by-sqlyog.html
http://webyog.com/faq/content/34/148/en/do...y-language.html

The option to specify CHARSET with MySQL 'LOAD DATA' command was added recently (around 5.0.32 or so). We support that now.


The CHARSET option is a client-side specification. If SQLyog detects the file as UTF8 or UCS2 just let it be like that! The server will store as the database/table is defined but it will be decoded as specified with CHARSET option during import. It is a server functionality - not a SQLyog functionality.


This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.