I am really confused about how to write sql code on sql editor. I have some special characters are some of russian,some of turkish some of japon. When i try to paste a sql code including these char, sql editor cannot read them and replacing them with “?”.
ex:
insert into t_retailers values (455,‘RU’,‘Интернет-магазин Sony Style’,sysdate,‘CDBLOAD’,sysdate,‘CDBLOAD’,1);
insert into t_retailers values (456,‘RU’,‘Другое’,sysdate,‘CDBLOAD’,sysdate,‘CDBLOAD’,1);
in this example special chars are replacing with “?” on sql navigator sql editor or toad sql editor ?. Where can i set up the encoding type of these editors ?
Unfortunately, we’re currently not supporting multibye in the editors. However, if you’re using 5.5 and above, we do support multibyte in the data grid so instead of running these statements to insert records you can manually enter them into a grid. Please check out the Beta threads if you want to try our beta build. (the current GA is 6.0)
how can i insert below query without any damage ? When i copy and paste it on sql editor it is corrupting?
insert into t_retailers values (455,‘RU’,‘Интернет-магазин Sony Style’,sysdate,‘CDBLOAD’,sysdate,‘CDBLOAD’,1);
insert into t_retailers values (456,‘RU’,‘Другое’,sysdate,‘CDBLOAD’,sysdate,‘CDBLOAD’,1);
Hi,
Like I stated before, SQL Navigator doesn't support the multi-byte characters in the sql scripts (because of limitations of the third-party database access component we use) that's why the data is corrupting. This feature will be added in the future.
If you want to insert these records, you have to MANUALLY paste in the Russian record into the data grid or the table editor. Because your data is in different languages (Russian, japanese, etc. ) you have to use SQL Nav 6.0 because it supports multiple-languages. Please refer to the snapshots to locate the data grid and table editor in SQL Nav 6.0.
Hi,
Like I stated before, SQL Navigator doesn’t support the multi-byte characters in the sql scripts (because of limitations of the third-party database access component we use) that’s why the data is corrupting. This feature will be added in the future.
If you want to insert these records, you have to MANUALLY paste in the Russian record into the data grid or the table editor. Because your data is in different languages (Russian, japanese, etc. ) you have to use SQL Nav 6.0 because it supports multiple-languages. Please refer to the snapshots to locate the data grid and table editor in SQL Nav 6.0.
Thank you for your efford. I have just find one free way for this problem. Oracle sql developer is supporting multibyte and it is free. When i buy sql navigator 6.0 i will try it.
Thanks for the valuable feedback… We made the decision to warn encoding every time when a file containing non-ascii characters is saved in ANSI encoding. Apparently some users like you would like to save those international characters supported by local system in ANSI. Such ANSI files work without any problems in local system, but no guarantee in other systems that may have different regions and language (locale) settings. I would suggest people to save such files in UTF-8 No BOM.
However, you raised a good point here. SQLNav should not warn for encoding since those files used to work fine in the system, and notepad & notepad++ don’t warn anything either when the contents can be handled in local system. We will change the method to check encoding and only warn it when necessary (such as saving Chinese in the system which sets French as the language for non-Unicode programs).
