What are the challenges you face when working across database platforms? Take the survey
Options

Script coding

Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
edited November 25, 2005 10:47AM in SQL Compare Previous Versions
Hi Lazlo,

If I understand correctly, the scripts were always in UTF-8. There used
to be a UTF preamble in the first 2 bytes, though, that specified that the
file was Unicode (an oversight on our part). In 3.15 that was taken out to
make it easier for programmers to read and write the scripts as bytes
without having to skip the first two bytes, and for legacy applications like
isql to read the files.

Regards,

Brian Donahue
Red Gate Technical Support

"Laszlo Fenyo" <pine@ndpo.novodata.hu> wrote in message
news:AZX5SPiJEHA.1616@server53...
> Versions previous to 3.15 saved SQL scripts in Unicode format, so all
> special, accented characters were readable in Query Analyzer. Now version
> 3.15 saves synchronization scripts in UTF-8, so we have to convert it to
> Unicode before we open these scripts in QA.
> Is it a bug or a feature?
>
> Laszlo
>
>

Comments

  • Options
    This issue has been taken care of. You may now save the synchronization scripts in several formats: ASCII, UTF-8, UTF-8 without preamble, and Unicode.

    This should pretty much satisfy any program's requirements for being able to read the script correctly.
This discussion has been closed.