[LONG] Sybase DB-Lib discussion

Sorry about the length. The Sybase DB-Lib now has an optional "charset" parameter to the "connect" functions. This feature is not supported by FreeTDS, and there are a few bugs reports about it. I thought of a couple possible solutions, and am looking for opinions on any one of them, or other ideas. Please keep in mind that these are *just* ideas. I'm not trying to start any holy wars here...at the very least, I expect that some of these will spark some good discussion. =) 1) Close bug reports. This is really *not* a PHP Bug. Personally, I feel this would be the least desirable of the available solutions. While this is true, I feel that the *right* thing to do here is to handle this gracefully somehow. If this option is taken, it might be nice if we at least contacted the FreeTDS guys and informed them of it, and perhaps made it a FAQ. I would be willing to volunteer to get with FreeTDS on this, but I'm guessing some of you out there probably already *know* the FreeTDS guys, and so would be better qualified. 2) Tell those people using FreeTDS to use Sybase CT-Lib. While I've never used FreeTDS myself, I'm given to understand that it supports both protocols. Actually, this brings up something else...the PHP DB-Lib module is still a bit buggy. I'm no longer actively using it, but there are a number of bug reports on it. DB-Lib itself has been deprecated by Sybase. Not being an expert here, I'm not sure if there are strong reasons to hang onto DB-Lib. One thing that has crossed my mind is making --with-sybase do CT-Lib, and make them explicitly request DB-Lib (--with-sybase-db). 3) Fix FreeTDS. Obviously, this is not the forum for discussing this, but it should be considered as an option. 4) Detect if FreeTDS is the library and #if protect the code in question Not sure if this is possible, though I wouldn't be surprised. This has the drawback of clutter in the code, possibly others. 5) Remove the charset param.