Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. Chinese characters in SELECT query

Chinese characters in SELECT query

Scheduled Pinned Locked Moved Database
databasejsonquestion
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V Offline
    V Offline
    Varghese Paul M
    wrote on last edited by
    #1

    Hi friends, I am working with SQLServer 2005 database (Collation set as Chinese) using odbc api SQLExecDirect and SQLExecute. Some of my SELECT queries containing some chinese characters works fine with SQLExecute and SQLExecDirectW but NOT with SQLExecDirect. My gut feeling is SQLExecute is converting the query into unicode before it executes. Is this assumption right ? thank you

    cheers Varghese Paul

    W 1 Reply Last reply
    0
    • V Varghese Paul M

      Hi friends, I am working with SQLServer 2005 database (Collation set as Chinese) using odbc api SQLExecDirect and SQLExecute. Some of my SELECT queries containing some chinese characters works fine with SQLExecute and SQLExecDirectW but NOT with SQLExecDirect. My gut feeling is SQLExecute is converting the query into unicode before it executes. Is this assumption right ? thank you

      cheers Varghese Paul

      W Offline
      W Offline
      Wendelius
      wrote on last edited by
      #2

      This would depend on the driver and it's implementation. One problem you may encounter is: http://support.microsoft.com/kb/271198[^]. However, if SQLExecDirectW is working, why not use it instead of SQLExecDirect.

      The need to optimize rises from a bad design.My articles[^]

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups