Bug #53868 Files saved on Windows are using UNIX EOL instead of Windows EOL
Submitted: 20 May 2010 20:12 Modified: 23 May 2010 13:07
Reporter: Orlando Colamatteo Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.1.21 OSS RC Rev 5918 OS:Microsoft Windows (Windows 7 64-bit)
Assigned to: CPU Architecture:Any
Tags: sql editor, Windows EOL

[20 May 2010 20:12] Orlando Colamatteo 
Description:
.sql files saved from Workbench SQL Editor contain UNIX EOL characters instead of Windows EOL (Environment.NewLine) characters.

How to repeat:
From Windows, save a .sql file from SQL Editor with at least one line break in it. Open the file in a hex editor and notice that the line break is represented as a UNIX EOL instead of a Windows EOL.

Suggested fix:
Use the platform-appropriate EOL character when saving.
[21 May 2010 9:18] Valeriy Kravchuk 
It is easy to verify. This is how script is saved on Windows:

0000000000:  73 65 6C 65 63 74 20 31 │ 3B 0A 73 65 6C 65 63 74  select 1;◙select
0000000010:  20 32 3B 0A             │                           2;◙

But it should not be a problem for any proper text editor, may be related to multiplatform nature of Workbench and is not a big deal in general, IMHO. I'd consider this as a feature request.
[23 May 2010 13:07] Alfredo Kojima 
Duplicate of bug #51308