[peterlaursen]

You should be able to see the alter table statement in HISTORY tab (unless it exceeds 4 KB in size >> http://www.webyog.com/faq/28_89_en.html) – also if it is unsuccessfull

[peterlaursen]

For server directives to take effect the Server must be restarted.

Messing around with the MySQL files the way you do is not wise!

[peterlaursen]

FAQ: http://www.webyog.com/faq/28_89_en.html

[peterlaursen]

But there is a FAQ to write here, I guess.

Nice work if you can get it! :huh:

EDIT: I see Ritesh was here too!

[peterlaursen]

The ALTER TABLE statement is too big!

Statements bigger than 4 KB are not logged to HISTORY. the reaon is that HISTORY is kept in memory. And to avoid memory use 'build up' this limit was introduced (I think with 4.07 or around that time). Statements kan be MB's, GB's in size …

The 4K limit is not configurable.

I feel like to repeat my request that HISTROY is spooled to a file and not kept in memory! <_< . Also a statement like

Code:

ALTER TABLE blabla (abbreviated by SQLyog)

in HISTORY would be nice!

I saved the CREATE statement. It is 3,67 KB. ALTER syntax takes a little more. So I guess you just exceeded the limit!

EDIT: I can add that actually it was some af my data that gave cause for this. I have a database with very big photographs (48 bit TIFF-format – each file is around 35 M:cool:. When inserting a lot of those pics history took all available memory. Next system began to swap and everything became incredible slow!

[peterlaursen]

So … try making both integers UNSIGNED.

[peterlaursen]

With MyISAM tables I think the directive will work also with MySQL < 4.1.13. That is how I read the docs. Am I wrong? If you are sure to have experienced that it is the same with MyISAM I'll change the FAQ accordingly.

[peterlaursen]

1) Comments.

Well actually it is the plan that with version 5.1 the STRUCTURE SYNC tool shall be completely finished. So I second this request. It should not be allowed to delay the release of 5.1 I think, but then it could be added with a 'service release' (5.1.x)

2) Error in ALTER TABLE.

I am not sure that I understand this. When you copy to file or clipboard you get the complete query – all CREATE, ALTER and DROP statements. And the errors that you might get are errors sent by the server. But you should not get errors! What kind of error do you get? Is this issue/question/request also related to the STRUCTURE SYNC tool or just the common ALTER TABLE -functionality?

[peterlaursen]

You can also use 'MySQL Administrator'

The meaning of 0,1 and 2 for this directive is explained in attached screenshot.

[peterlaursen]

Looks very much like this one:

http://www.webyog.com/faq/26_25_en.html

It should solve the issue to upgrade to MySQL 4.1.13 or higher.

… and use the server directive lower_case_table_names=2 in the [mysqld] section of the my.ini -file.

[peterlaursen]

BTW: did you consider to upgrade SQLyog?

Also the Backup Tool has been quite a lot improved since 3.71.

Though it will not change this.

[peterlaursen]

MySQL 5.1.5 is here now!

ftp://sunsite.dk/mirrors/mysql/Downloads/MySQL-5.1/

[peterlaursen]

The next battle of the war has started.

MySQL just relesed binaries for php5.1.2 connection!

ftp://sunsite.dk/mirrors/mysql/Downloads/Connector-PHP/

[peterlaursen]

Just one more follow up. The MySQL 5.1.5 tree has been closed, so it will probably be available for download very soon.

5.1.5 adds a new feature: XML document handling. It is VERY interesting in my opinion! http://dev.mysql.com/tech-resources/articl…ql-5.1-xml.html

5.1.6 will add an EVENT feature: at feature to schedule execution of SQL-statements. Compared to SQLyog 'Notifications Services' it has the advantage that it is implemented with the server itself so no client must connect to trigger an EVENT. However it is not as flexible as NS – for instance you may schedule an EVENT with more statements but there is no way to predict in what order they are executed (!). Not completely useless but also not very interesting in my opinion. Judge yourself: http://dev.mysql.com/tech-resources/articl…nt-feature.html.

[peterlaursen]

aha …

http://php.mirrors.ilisys.com.au/manual/en/ref.pdo.php

the PDO dll is the new 'database abstraction layer' as of PHP 5.1.x

I never used it with PHP 5.1.0 and 5.1.1 (was not aware that it came with a new extension compared to 5.0.x, but now it is activated in 5.1.2 here.

Don't know how much difference it makes, but it works OK 🙂

[Author]

Posts