notepad 4.1.2 and 4.2.2 (I tried the latest) crashes if it finds an SQL statement in the file it is attempting to open. Windows XP Professional, Dell D600 laptop.
I have a file with the following contents:
set line length 8096;
select * from table_name;
COLUMN1 COLUMN2 COLUMN3 COLUMN4 etc etc etc
Data1 Data2 Data3 Data4
etc
etc
etc
The length of each line record is 1011 characters long and there are 80 records in the file.
Notepad and wordpad open the file fine, but notepad++ crashes.
If I remove the SQL statement from the file, notepad++ opens it fine(i.e. remove: select * from table_name;)
So, it looks like Notepad+= has issues with SQL statements where the record length is long in a file.
It must be trying to interpret the file as actual SQL code, rather than SQL output.
Perhaps Notepad++ could check the file type first and if it's .TXT, then ask if you want notepad++ to interpret it as SQL source or not?
Perhaps catching the condition instead of crashing would be better too?.
:-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As an addendum to my post about "Notepad crashes if SQL statement is in file", I do understand that notepad++ IS a coders editor and the file I was editing wasn't code, but rather output, but even so, I thought I'd mention about the program crash anyhow - a program should not just crash - it should try and give some reaosn as to why it cannot handle what it was being asked to do.
:-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
notepad 4.1.2 and 4.2.2 (I tried the latest) crashes if it finds an SQL statement in the file it is attempting to open. Windows XP Professional, Dell D600 laptop.
I have a file with the following contents:
set line length 8096;
select * from table_name;
COLUMN1 COLUMN2 COLUMN3 COLUMN4 etc etc etc
Data1 Data2 Data3 Data4
etc
etc
etc
The length of each line record is 1011 characters long and there are 80 records in the file.
Notepad and wordpad open the file fine, but notepad++ crashes.
If I remove the SQL statement from the file, notepad++ opens it fine(i.e. remove: select * from table_name;)
So, it looks like Notepad+= has issues with SQL statements where the record length is long in a file.
It must be trying to interpret the file as actual SQL code, rather than SQL output.
Perhaps Notepad++ could check the file type first and if it's .TXT, then ask if you want notepad++ to interpret it as SQL source or not?
Perhaps catching the condition instead of crashing would be better too?.
:-)
As an addendum to my post about "Notepad crashes if SQL statement is in file", I do understand that notepad++ IS a coders editor and the file I was editing wasn't code, but rather output, but even so, I thought I'd mention about the program crash anyhow - a program should not just crash - it should try and give some reaosn as to why it cannot handle what it was being asked to do.
:-)
> but even so, I thought I'd mention about the program crash anyhow
> - a program should not just crash
Sure. You're right.
Could you rename the directory "plugins" (in the Notepad++ installed dir) to whatever then relaunch Notepad++ and try it again?
Please let me know the result.
Don