Hi,

I'm looking into adding unicode support for odbconnection. Although the unixodbc and iodbc drivers also support the W versions of the API I would prefer to include the W versions with a define. Is there already a global define to select unicode api's? Or is this going to be managed on a per unit/package level?

Thanks, Ludo

In our previous episode, Ludo Brands said:

No. There is UNICODE, but that only covers some recent additions. And most of the database systems are loadlibrary style anyway.

The bulk of the header applications were simply done without it.

I'm in the middle of adding the unicode versions in the header translation. That's why I'm asking.

The other database systems support unicode data without a unicode api. The MS odbc driver manager plainly refuses to report unicode data as SQL_WVARCHAR when connecting with the Ansi api.

Thanks,

Ludo

In our previous episode, Ludo Brands said:

I'm in the middle of adding the unicode versions in the header translation. That's why I'm asking.

Start small, by submitting small pieces. Usually insights progress as we go, and exceptions to the original perceived rules are discovered ;)

3 months now that the patch was submitted and no reaction since. Unfortunately it wasn't a small piece as requested since I didn't find a way to implement, say, 1/10th of unicode. Don't know if it made "insights progress" or help "discover exceptions to the original perceived rules". What I do know is that this and other patches (some solving real bugs) sitting there in mantis waiting to be looked at has brought my motivation for contributing patches to sqldb to an all time low.

Ludo