- February 22, 2021 at 5:14 pm #27315
I work primarily with SQL files and different databases. In my case, and for brevity, I added a MySQL and Oracle configurations.
I switch between creating or opening a file as needed and came to observe that EmEd sometimes changes an already open file with say MySQL configuration to Oracle one.
I still can’t reliably reproduce this annoyance, but it happened enough time to open the bug fix request.
Thank you.February 23, 2021 at 1:50 pm #27317Yutaka EmuraKeymaster
Can you write a step-by-step procedure to reproduce the issue?
Are the file extensions associated with each configuration at Associate Configurations on the Tools menu? What are those file extensions?February 23, 2021 at 7:54 pm #27321
I do not know if the forum picks my replies as I do not see my replies.
So basically I was able to reproduce it the easy way:
1. Ensure you download and install both the MySQL and PLSQL syntaxes
2. Open or create and save one MySQL and one PLSQL file with the .sql extension (I think for one I changed what sql opens with, but unsure)
3. So you now have two saved .sql files with content under each syntax flavour open, then say you are on the MySQL syntax file, create a new file and save it, in my case the file(s) that I had set to MySQL syntax turns changed to PLSQLFebruary 24, 2021 at 9:53 am #27328Yutaka EmuraKeymaster
I am not sure if I understand your question. You usually need to have unique file extensions associated with each configuration. If both MySQL and PLSQL files have *.sql file extension, how can EmEditor know which configuration you want to open with? Please clarify your issue.February 24, 2021 at 6:03 pm #27333
The issue is, it changes the syntax already chosen for a file that has the syntax already assigned, if I create a new file.
EmEditor knows what I set it to because I did, it changes it in unsanctioned manner under the aforesaid circumstances.
As a side note, I noticed in either of these “SQL” files there is changed lines detection happening – no yellow vertical bar despite it being set. There is no green on save either.February 26, 2021 at 10:58 pm #27342Makoto EmuraKeymaster
ArthurZ, can you confirm if I understood you correctly? You created a new MySQL file and a PLSQL file and saved them both with a .sql extension. You switched to the MySQL file, then created a new PLSQL file. The previous MySQL document changed to PLSQL configuration.
Could you tell us your EmEditor version from the About EmEditor dialog?February 27, 2021 at 6:15 pm #27344
The 1st part: >”You created a new MySQL file and a PLSQL file and saved them both with a .sql extension” <–Yes
The 2nd: > “You switched to the MySQL file, then created a new PLSQL file” <– not switched but created a new using say the MySQL configuration,
Lastly > “The previous MySQL document changed to PLSQL configuration” <– Yes.
It was back then the latest stable. I upgraded two minor once, but do not know if the issue remains as I did not work yet with SQL. But I plan to.February 27, 2021 at 7:59 pm #27345Makoto EmuraKeymaster
I could not reproduce in 20.5.6. I understand it doesn’t happen all the time. I recommend setting your PLSQL file extension to .pls. That should make it easier for you and for programs to recognize the SQL type.
- You must be logged in to reply to this topic.