Re: Remove unicode from SQL

From: Keith (mcgillivrayk_at_prodigy.net)
Date: 08/24/04

  • Next message: VisionSet: "Criteria objects" 
    Date: 23 Aug 2004 18:30:47 -0700

    Joe,

    It seems as if there is a patch for JTurbo 3.0.1 that has this fixed.
    The property setting isn't needed.

    Thanks for your help.

    Keith

    Joe Weinstein <joeNOSPAM@bea.com> wrote in message news:<41276ADD.5060202@bea.com>...
    > Keith wrote:
    >
    > > Joe Weinstein <joeNOSPAM@bea.com> wrote in message news:<4126D9C3.8050607@bea.com>...
    > >
    > >>There should be a driver property you can define to stop the driver doing
    > >>that. All commercial drivers I know of do. The default should be to do as the
    > >>driver does, to ensure that any valid Java string (16-bit characters) get sent
    > >>to the DBMS unchanged. However, for varchar values and indexes it makes the
    > >>DBMS have to convert back to varchar, and the conversion means that the DBMS
    > >>will skip indexes and do table scans (slow).
    > >>Joe Weinstein at BEA
    > >>
    > >
    > > Thanks Joe.
    > > Is this the property that you are refering to on JTurbo?
    > > SendStringParametersAsUnicode={true | false}.
    > > Determines whether string parameters are sent to the SQL
    > > Server database in Unicode or in the default character
    > > encoding of the database. True means that string parameters are sent
    > > to SQL Server in Unicode.
    > > False means that they are sent in the default encoding.
    >
    > That's it. Set it to false.
    > Joe

  • Next message: VisionSet: "Criteria objects"