Re: FreeTDS Digest, Vol 73, Issue 1
"Federico Alves" <[email protected]>
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <02e301c9849b$0d052c90$270f85b0$@com> |
I have a SQL 2008 server available for the project, permanently. Please Frediano contact me via email or on Skype and I will give you full control of the box. My business is 100% freetds+sql2008 and ODBC. Federico -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Sunday, February 01, 2009 1:21 PM To: [email protected] Subject: FreeTDS Digest, Vol 73, Issue 1 Send FreeTDS mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://lists.ibiblio.org/mailman/listinfo/freetds or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of FreeTDS digest..." Today's Topics: 1. Announcement: db-lib update (James K. Lowden) 2. Re: SQL Server 2008: Support for TIME(n) data type (James K. Lowden) 3. Compiling under HPUX IA64 (Michael Warchut) ---------------------------------------------------------------------- Message: 1 Date: Sat, 31 Jan 2009 14:58:45 -0500 From: "James K. Lowden" <[email protected]> Subject: [freetds] Announcement: db-lib update To: TDS Development Group <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=US-ASCII Two changes coming to the db-lib API: 1. Functional prototypes to use "const arg[]" instead of "char *" wherever applicable. 2. Removal of all unimplemented functions from sybdb.h and libsybdb. The vendors -- each for their own reasons -- stopped updating db-lib years ago. Microsoft hasn't produced a new binary since 2000 and no longer distributes even that. Meanwhile, the C standard and common practice has changed. const was added to the language and the C standard library is described in const terms. Old programs are unaffected, but new programs that adopt modern practice encounter warnings/errors when passing a const string to a stone-age function, e.g.: RETCODE dbrpcinit(DBPROCESS * dbproc, char *rpcname, DBSMALLINT options); which is now (in CVS HEAD): RETCODE dbrpcinit(DBPROCESS * dbproc, const char rpcname[], DBSMALLINT options); Not done, but under consideration, is to declare as "const DBPROCESS*" those functions (e.g. dbconvert) that don't modify the DBPROCESS structure. That would facilitate C++ wrapper library development. Of which there are many, I'm sure. ;-) On the second point, the FreeTDS db-lib declared (and sometimes defined) 78 functions that have no useful implementation. I've never understood why that was done; I don't see the point in helping something compile that won't link, or linking something that will only come to tears when it runs. Perhaps once upon a time programs linking to FreeTDS might have referenced some functions that were rarely used, and linking to stub-functions permitted them to partially run with FreeTDS. Nowadays substantially all the API has been implemented, and much of what remains has been scheduled for "never". Consequently, I moved all such code inside conditional compilation. If you want it, define DBLIB_UNIMPLEMENTED. I did this as a favor to developers. If your code fails to compile/link without DBLIB_UNIMPLEMENTED, you know you're uing non-code and you now have an opportunity to find it and strike it. Or, you can modify your Makefile and go on as before. Feedback welcome of course. --jkl ------------------------------ Message: 2 Date: Sat, 31 Jan 2009 15:31:19 -0500 From: "James K. Lowden" <[email protected]> Subject: Re: [freetds] SQL Server 2008: Support for TIME(n) data type To: FreeTDS Development Group <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=US-ASCII Frediano Ziglio wrote: > About TIME(n)... aehmm... I don't know James free time but I'm very > busy To continue to thrive, FreeTDS needs ODBC development talent and server support. I get involved with ODBC from time to time because I need FreeTDS to work with DBD::ODBC. But I have an allergy to ODBC. It gives me a rash but (for good or ill) no itch. Frediano brought the ODBC driver into the 21st century. Without his continuing contribution, it is apt to languish somewhat, much as the ct-lib library does these days. If you use the ODBC driver, you would be well advised to take note. API development is challenging and interesting (I should know!), and I encourage the interested user to apply his energies and talents to it. That is how FreeTDS came to be, and that is how it will grow. And you will learn something, I promise. Another constraint is that the project has no 2008 server available to it. (Yes, I know, it's a free download, but one needs a Windows box and the inclination to set it up.) For this reason, Frediano does all the 2008-specific testing. Should patches magically rain down on me alone, I would have to choose between putting them in unverified and setting them aside. So, dear reader, it comes to this: If you want ODBC to support SQL Server 2008, my advice is to make a server available, or join the project, or both. --jkl ------------------------------ Message: 3 Date: Sun, 1 Feb 2009 09:03:14 -0800 From: "Michael Warchut" <[email protected]> Subject: [freetds] Compiling under HPUX IA64 To: <[email protected]> Message-ID: <1f6601c9848e$f8f26f30$ead74d90$@com> Content-Type: text/plain; charset="US-ASCII" From: Michael Warchut [mailto:[email protected]] Sent: Friday, January 30, 2009 10:08 AM To: '[email protected]' Subject: Compiling under HPUX IA64 Hello I am a long time Freetds user but usually on Linux. Now I have a pair of RX8640 servers running HPUX IA64. I am trying to get FreeTDS .84 to compile and run under this platform but have run into copious errors from compile errors to make check failures. Are there any special tools that need to be installed from GNU to replace the stock HPUX set to make this work? Any other tips? I recently got .82 to compile but when I try to connect to a SQL 2005 server this is what I get in the error log. 13:24:18.357341 17237 (log.c:190):Starting log file for FreeTDS 0.82 on 2009-01-30 13:24:18 with debug flags 0xffff. 13:24:18.357573 17237 (iconv.c:78):Using trivial iconv 13:24:18.357609 17237 (iconv.c:197):names for ISO-8859-1: ISO-8859-1 13:24:18.357621 17237 (iconv.c:197):names for UTF-8: UTF-8 13:24:18.357633 17237 (iconv.c:197):names for UCS-2LE: UCS-2LE 13:24:18.357646 17237 (iconv.c:197):names for UCS-2BE: (null) 13:24:18.357658 17237 (iconv.c:363):iconv to convert client-side data to the "roman8" character set 13:24:18.357748 17237 (iconv.c:477):tds_iconv_info_init: use memcpy to convert "ROMAN8"->"UCS-2LE" 13:24:18.357772 17237 (net.c:210):Connecting to 172.16.140.23 port 1433 (TDS version 8.0) 13:24:18.358050 17237 (net.c:264):tds_open_socket: connect(2) returned "Operation now in progress" 13:24:18.358133 17237 (net.c:303):tds_open_socket() succeeded 13:24:18.358145 17237 (util.c:162):Changed query state from DEAD to IDLE 13:24:18.358160 17237 (login.c:735):quietly sending TDS 7+ login packet 13:24:18.358215 17237 (token.c:312):tds_process_login_tokens() 13:24:18.359100 17237 (util.c:334):tdserror(6000000000014800, 6000000000029650, 20017, 0) 13:24:18.359745 17237 (util.c:368):tdserror: client library returned TDS_INT_CANCEL(2) 13:24:18.359759 17237 (util.c:389):tdserror: returning TDS_INT_CANCEL(2) 13:24:18.359785 17237 (util.c:162):Changed query state from IDLE to DEAD 13:24:18.359798 17237 (token.c:316):looking for login token, got 0() 13:24:18.359816 17237 (token.c:108):tds_process_default_tokens() marker is 0() 13:24:18.359829 17237 (token.c:111):leaving tds_process_default_tokens() connection dead 13:24:18.359842 17237 (util.c:334):tdserror(6000000000014800, 6000000000029650, 20002, 0) 13:24:18.360522 17237 (util.c:368):tdserror: client library returned TDS_INT_CANCEL(2) 13:24:18.360536 17237 (util.c:389):tdserror: returning TDS_INT_CANCEL(2) 13:24:18.360551 17237 (mem.c:563):tds_free_all_results() Thanks so much in advance. Michael ------------------------------ _______________________________________________ FreeTDS mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/freetds End of FreeTDS Digest, Vol 73, Issue 1 **************************************