This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: SQL Scripts and encoding
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 25, 2008
05:09 AM
SQL Scripts and encoding
Sql Scripts work just fine until I want to insert/update non-english text:
INSERT INTO Table VALUES(..., 'Non-english text', ...).
What encoding does installshield use to perform such queries?
INSERT INTO Table VALUES(..., 'Non-english text', ...).
What encoding does installshield use to perform such queries?
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 25, 2008
04:59 PM
Try adding a preceding N to the record data in the INSERT statement as follows, and see if it solves your issue:
INSERT INTO Table VALUES(..., N'Non-english text', ...)
If you are using an ANSI script file, InstallShield will use the current Windows system code page on the target system. You may need to use a Unicode script file in order to solve your issue.
INSERT INTO Table VALUES(..., N'Non-english text', ...)
If you are using an ANSI script file, InstallShield will use the current Windows system code page on the target system. You may need to use a Unicode script file in order to solve your issue.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 25, 2008
11:02 PM
hidenori wrote:
Try adding a preceding N to the record data in the INSERT statement as follows, and see if it solves your issue:
INSERT INTO Table VALUES(..., N'Non-english text', ...)
Didn't help...
hidenori wrote:
You may need to use a Unicode script file in order to solve your issue.
If I have script in UTF-8, installshield shows bad symbols in editor and doesn't even exucute such query
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 26, 2008
11:41 AM
The SQL feature currently does not support the UTF-8 file format. Please convert it to the Unicode file format manually using a text editor such as Notepad.exe.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 29, 2008
12:13 AM
Unfortunately I didn't get it to work (((
What I tried:
1) Script file in ANSI created in IS IDE. Inserts bad symbols to oracle database.
2) Script file created in UTF8 and imported (or inserted) to IS (BTW, IS refuses to show script in unicode). Inserts bad symbols...
3) Script file created in UTF16 and imported (or inserted) to IS. Inserts bad symbols...
Please help!
What I tried:
1) Script file in ANSI created in IS IDE. Inserts bad symbols to oracle database.
2) Script file created in UTF8 and imported (or inserted) to IS (BTW, IS refuses to show script in unicode). Inserts bad symbols...
3) Script file created in UTF16 and imported (or inserted) to IS. Inserts bad symbols...
Please help!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 29, 2008
09:39 AM
If you run those same script files from an Oracle's client tool such as SQL*Plus, is the record updated as you expect?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 10, 2009
12:20 AM
SQLPlus can't execute neither utf8 or unicode script file. Can't recognize initial symbols before insert statement: "unknown command beginning "п»їinsert ..." - rest of line ignored"
It works only if script file is in native codepage (Win-xxxx). And it's fine - no bad symbols
It works only if script file is in native codepage (Win-xxxx). And it's fine - no bad symbols
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 10, 2009
11:18 PM
I also noticed that if I copy and paste text with non-english symbols to notepad from Installshield script window, text becomes invalid. Just like I can't write non-english symbols to any string field in IS (product name for example), because they become invalid. So I have to use string table...
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)