Skip to Content.
Sympa Menu

freetds - [freetds] status

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "ZIGLIO Frediano" <Frediano.Ziglio AT vodafone.com>
  • To: <freetds AT lists.ibiblio.org>
  • Subject: [freetds] status
  • Date: Thu, 25 Sep 2003 12:17:56 +0200

There are still some issue but I think is time for a roadmap to 0.62
version.

Many issues concern iconv stuff.

- support string conversions for Sybase

We can skip this for now...

- support different column charset under mssql2k

Post or implement in 0.62 ?

- convert string using input parameters

Input parameters are not converted. Code do not core but someone can
report
strange problems if server charset <-> client charset are very
different

- finish support for no-GNU iconv (indirect conversion see
src/tds/iconv.c)

HP/UX and other require indirect conversions...

- borrow GNU's libiconv m4 macro to test/provide EILSEQ

?? what's is this ?

- add test for locale_charset() to configure.in. Use it if available
instead of nl_langinfo, because it implies we're using GNU iconv

In previous versions we always used ISO-8859-1 as our default
charset,
only tsql set another charset. Should freetds use system default
charset as its default ?

- walk through charset name initialization. Make sure it works in the
absence of an entry in freetds.conf

?? fixed ?

- pass any internal hard-coded charset names through
tds_canonical_charset_name()

?? why ? fixed ?

- the supporting .h file will need adjustment for non-GNU iconv

??

- input name "ASCII" must always have a canonical form.

now we use ISO-8859-1 to convert freetds string to client.
I don't think this is a problem so we can post this stuff


Others concern ODBC. It's quite stable however many things went in 0.62
code so
there are still some issues related to compatibility and others.
Prepared statement need adjustement (blobs for Sybase, SQLPutData). This
stuff
used to work in 0.61 so it's a good thing to fix it before 0.62.
The good thing I discovered is that output parameters under ODBC are
only supported
for RPC, so I can use TDS_LANGUAGE under Sybase for binary data (very
useful for
optimizing bandwidth on blobs instead of converting all to a language
string)


Tests. There are 4 tests that do not work:
- ctlib lang_ct_param under mssql. Not a delaying problem. It never
worked :)
- odbc type. related to some ODBC3 new issues
- odbc putdata. See above
- odbc binary_test under Sybase. See above

Is it time for a beta release ?

freddy77




Archive powered by MHonArc 2.6.24.

Top of Page