MySQL Bugs: #12929: Console pasting does not work well on Windows 2000

Bug #12929	Console pasting does not work well on Windows 2000
Submitted:	1 Sep 2005 14:04	Modified:	6 Oct 2005 0:55
Reporter:	Martin Olsson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	mysql Ver 14.7 Distrib 4.1.12, for Win3	OS:	Windows (win2000)
Assigned to:	Sergey Vlasenko	CPU Architecture:	Any

Description:
Can't you just create a better console tool instead of building it inside a DOS-box. The command line interface in Windows 2000 is too stiff and really hard to work with. 

How to repeat:
1. Install this version of MySQL on a Windows 2000 system:
mysql  Ver 14.7 Distrib 4.1.12, for Win32 (ia32)

2. Start up the MySQL Command Line Client

3. Paste these SQL statements into the DOS-box:

CREATE DATABASE IF NOT EXISTS databasen;
USE databasen;
CREATE TABLE IF NOT EXISTS qmtbl_users(user_id INT NOT NULL AUTO_INCREMENT, username TEXT, password TEXT, registration_date DATETIME, last_seen DATETIME, image_mime TEXT, image_data MEDIUMBLOB, realname TEXT, email TEXT, PRIMARY KEY (user_id));
CREATE TABLE IF NOT EXISTS qmtbl_quizes(quiz_id INT NOT NULL AUTO_INCREMENT, owner_user_id INT, public_quiz BOOL, title TEXT, creation_date DATETIME, last_finished DATETIME, times_finished INT, PRIMARY KEY (quiz_id), FOREIGN KEY (owner_user_id) REFERENCES qmtbl_users (user_id));

Now you will notice that the last line wasn't correctly pasted, possible because it's too long? I dunno if this applies to Windows XP too but it's really annoying.

Suggested fix:
Even if you build a simple GUI tool you can still design it as a console etc, just with the ability to properly paste stuff etc.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/29374

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/29962

Fix is available in 4.1.15 & 5.0.14

Noted in 4.1.15, 5.0.14 changelogs.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/30750