http://permalink.gmane.org/gmane.comp.db.tds.freetds hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.db.tds.freetds/14524 <pre>I have downloaded and freetds-0.91 and when I run ./configure I get no errors. However when I try to make I get the following: Making all in include make all-am echo '#define FREETDS_SYSCONFDIR "/usr/local/etc"' &gt;freetds_sysconfdir.h Target "all-am" is up to date. Making all in src Making all in replacements source='iconv.c' object='iconv.lo' libtool=yes DEPDIR=.deps depmode=aix /bin/sh ../../depcomp /bin/sh ../../libtool --tag=CC --mode=compile cc -qlanglvl=extc89 -DHAVE_CONFIG_H -I. -I../../include -I../../include -I../../src/replacements -D_FREETDS_LIBRARY_SOURCE -D_REENTRANT -D_THREAD_SAFE -DDEBUG=1 -D_THREAD_SAFE -g -c -o iconv.lo iconv.c libtool: compile: cc -qlanglvl=extc89 -DHAVE_CONFIG_H -I. -I../../include -I../../include -I../../src/replacements -D_FREETDS_LIBRARY_SOURCE -D_REENTRANT -D_THREAD_SAFE -DDEBUG=1 -D_THREAD_SAFE -g -c -M iconv.c -DPIC -o .libs/iconv.o "iconv.c", line 484.7: 1506-356 (W) Compilation unit is empty. source='gettimeofday.c' obje</pre> Kevin Coyle 2012-05-25T18:01:49 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14523 <pre>Hi James, Thanks for the help. I wanted to follow up and let you know I found how to solve the problem. Since the field was an NVARCHAR I had to use a cast to Text in the select which fixed the issue. -Nate Nathan Sarr Senior Software Engineer River Campus Libraries University of Rochester Rochester, NY  14627 (585) 275-0692 nsarr&lt; at &gt;library.rochester.edu -----Original Message----- From: freetds-bounces&lt; at &gt;lists.ibiblio.org [mailto:freetds-bounces&lt; at &gt;lists.ibiblio.org] On Behalf Of James K. Lowden Sent: Friday, April 27, 2012 10:22 AM To: freetds&lt; at &gt;lists.ibiblio.org Subject: Re: [freetds] FreeTDS and out of Memor Error when trying to read diacritics On Thu, 26 Apr 2012 10:14:56 -0400 "Sarr, Nathan" &lt;nsarr&lt; at &gt;library.rochester.edu&gt; wrote: You want to make sure FreeTDS is encoding the data according to the client's expectation. The data have an encoding (sometimes incorrectly recorded) on the server. The client has one too, usually expressed with LC_LANG etc. FreeTDS converts between the two. To know </pre> Sarr, Nathan 2012-05-25T17:16:42 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14522 <pre>If Frediano or somebody from the team wants a SQL 2012 virtual machine, for development or testing, please let me know. The Vm will be provided with full administrative rights. Federico On 5/25/12 9:34 AM, "freetds-request&lt; at &gt;lists.ibiblio.org" &lt;freetds-request&lt; at &gt;lists.ibiblio.org&gt; wrote: </pre> Federico Alves 2012-05-25T15:08:14 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14521 <pre>2012/5/25 James K. Lowden &lt;jklowden&lt; at &gt;freetds.org&gt;: Try also to downgrade to 7.0 protocol. MS decided to not return textptr with data even they still support TEXTPTR function on T-SQL, or better, they decide to always return an invalid textptr! I don't remember if was with 7.1 or 7.2... I don't really understand why... Frediano _______________________________________________ FreeTDS mailing list FreeTDS&lt; at &gt;lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/freetds </pre> Frediano Ziglio 2012-05-25T14:39:50 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14520 <pre>On Fri, 25 May 2012 12:15:33 +0000 Trygve Liland &lt;Trygve.Liland&lt; at &gt;visma.no&gt; wrote: Those zeros are a problem, no doubt about it. Do the db-lib unit tests t0013.c and t0014.c work with your server? That would verify that dbwritetext() works with the TDS version you're using. The log doesn't record the value of the textptr returned by dbtxtptr. If the server is sending a NULL textptr, see if that changes using TDS 7.1. If not, if you're receiving a good textptr from the server, you need to find out why you're sending a NULL textptr. Hälsingar, --jkl </pre> James K. Lowden 2012-05-25T13:33:52 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14519 <pre>Hi We are doing a test using FreeTDS on Solaris moving a Fortran/C application from Sybase to MS-Sql server. Recently we ran into a problem I'm hoping to get a hint on how to solve. Simplified we are doing: - Update IMAGECOLTAB set IMAGECOL=NULL - Select IMAGECOL from IMAGECOLTAB - Get Pointer to IMAGECOL from dbtextptr - Get TimeStamp from dbtexttimestamp - Do dbwritetext with length of image to be written and NULL in last parameter - Loop text and do dbmoretext The problem is that we are getting tds_put_string: "writetext bulk IMAGECOLTAB.IMAGECOL 0x00000000000000000000000000000000 timestamp = 0x0000000000000000 with log" Invalid text, ntext, or image pointer value 0x00000000000000000000000000000000. Any idea on what we are doing wrong? I have checked code that we have in another program where we used dblib against Ms-Sqlserver, and I see more or less the same code. Below is a simplified C code for my function, and the resulting tds log file.</pre> Trygve Liland 2012-05-25T12:15:33 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14518 <pre>On Thu, 24 May 2012 22:53:50 +0000 Norman Chan &lt;nochan&lt; at &gt;ksbe.edu&gt; wrote: Not any longer, but that's a another story. :-) Yes, that answer still holds. The 0.91 release supports TDS 7.1 entirely and most of 7.2, and so basically acts like a 2005 client. Work is ongoing -- mostly by Frediano -- to support all protocol features for SQL Server 2010 in the development branch. That will be the basis for the next release one day. You will find SQL Server 2012 has datatypes not supported by the current release. I would advise you to be conservative in you DDL. Try to stick with what you know. If you're like most people, you'll be tempted to ask when the next release with all the cool new features will be available. The answer is we don't know. It's a spare-time project, and spare time is getting rare. Without more developers, we just can't stay current with Microsoft's releases. --jkl </pre> James K. Lowden 2012-05-25T02:21:36 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14517 <pre>Hello James thanks for the warm welcome. I should correct myself typo - it's FreeTDS http://www.freetds.org/ At your organization/office do you use FreeTDS to "talk" to SQL Server? My workplace is using that with SQL 2000 running on Windows and using an OSX PhP front-end for the web. I'm wondering if I could upgrade the database from SQL 2000 to SQL 2012. per the FAQ http://www.freetds.org/faq.html#What.is.FreeTDS maybe my question is answered: Does version X of FreeTDS connect to version Y of my Microsoft or Sybase server? "For the last several years, every version of FreeTDS has been able to communicate with every kind of TDS server. New servers sometimes introduce new protocol features, but the changes are small, and they're always compatible with old clients. Generally, you should use the latest version of the TDS protocol for your server. See the User Guide for details." -Norman -----Original Message----- From: freetds-bounces&lt; at &gt;lists.ibiblio.org [mailto:freetds-bounces&lt; at &gt;lists.ibib</pre> Norman Chan 2012-05-24T22:53:50 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14516 <pre>On Thu, 24 May 2012 00:15:46 +0000 Norman Chan &lt;nochan&lt; at &gt;ksbe.edu&gt; wrote: Welcome, Norman. Sorry, a quick googlelation of "tdsfree" didn't turn up anything obvious. What is this thing of which you speak? --jkl </pre> James K. Lowden 2012-05-24T22:38:32 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14515 <pre>Hello. Is there any way to handle TDS errors from PHP code? Here's what I'm trying to do: I'm working on user authorization using MsSql database login and password. The same login that is used to connect to MsSql database. Currently I'm just connecting to database and checking if the connection worked. If credentials are correct, everything works fine. But, if either login of password is wrong, my PDO connection just dies with this error: FreeTDS: db-lib: exiting because client error handler returned INT_EXIT for msgno 20002 And that also crashes my php session. Is there any way I can implement that client error handler on my PHP side, or it should had already been dealt by PDO_DBLIB? </pre> Николай Кудрявцев 2012-05-24T10:32:37 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14514 <pre>Hello, I am new to FREETDS. I'm working on as DBA Admin and owner of database on SQL 2000 sp3 We are currently using PHP version is 5.2.6 running on OSX Server using FreeTDS&lt;http://www.freetds.org/&gt; (ver 0.82) to communicate with MS SQL Server 2000. Can someone confirm my understanding of TDSfree? It's an API that works with SQL Server... Underneath the hood - it uses TDS specification to access the SQL Server database. (Therefore it does not need to have SQL Server Native Client drives, etc installed on machine housing webserver/php ) Separately: I wanted to ask the group if anyone has setup TDSfree with SQL 2012? Thank you for any help and info This message is the property of Kamehameha Schools and any attachments are confidential to the intended recipient at the e-mail address to which it has been addressed. If you are not the intended recipient, you may not copy, forward, disclose or use any part of this message or its attachments. If you received this transmission in error please notify </pre> Norman Chan 2012-05-24T00:15:46 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14513 <pre> On May 23, 2012, at 2:52 PM, James K. Lowden wrote: Right, it was an illustration from the past but an indication of trouble that could happen if we keep using the ChangeLog (as James has been doing). (and thanks for applying my patch) You might start with: % git checkout master Already on 'master' % git log branch-0_91..HEAD &gt; myChangeLog warning: refname 'branch-0_91' is ambiguous. and see what you want in myChangeLog that's not there. There are a *lot* of options to "git log". I believe the ambiguous ref warning is because we have a tag name that is the same as a branch name. I don't think, going forward, that tags should really have "branch" in their names. ________________________________________ Craig A. Berry mailto:craigberry&lt; at &gt;mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser </pre> Craig A. Berry 2012-05-24T00:12:44 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14512 <pre>On Wed, 23 May 2012 09:10:33 +0100 Frediano Ziglio &lt;freddy77&lt; at &gt;gmail.com&gt; wrote: How do I prepare a ChangeLog that details every commit since the previous release? I'd like to continue keeping ChangeLog in the distribution even if it's not a file managed by the SCM. For a release, I derive the news and readme files from ChangeLog. --jkl </pre> James K. Lowden 2012-05-23T19:52:17 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14511 <pre>2012/5/22 Craig A. Berry &lt;craigberry&lt; at &gt;mac.com&gt;: Yes, now we don't change ChangeLog every time, git log is enough, but at the time you did the patch we was still in cvs -&gt; git transition Applied. Frediano _______________________________________________ FreeTDS mailing list FreeTDS&lt; at &gt;lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/freetds </pre> Frediano Ziglio 2012-05-23T08:10:33 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14510 <pre>2012/5/21 James K. Lowden &lt;jklowden&lt; at &gt;freetds.org&gt;: Quite strange. Try to fetch tags again with git fetch --tags Frediano _______________________________________________ FreeTDS mailing list FreeTDS&lt; at &gt;lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/freetds </pre> Frediano Ziglio 2012-05-22T08:46:46 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14509 <pre> On May 19, 2012, at 7:57 AM, Frediano Ziglio wrote: It's usually enough, unless someone else has pushed since your last push. In that case you'll want to do "git pull --rebase" first in order to avoid spurious empty merge commits. They don't actually do much harm but they do create stupid-looking singularities in the commit history. I also think ChangeLog is now redundant and could be phased out. It even creates a genuine problem when trying to cherry-pick changes from master onto a maint branch when the ChangeLog was modified in the same commit as something else. Here's an example: % git checkout Branch-0_91 Switched to branch 'Branch-0_91' % git cherry-pick e6305b655e590c2 error: could not apply e6305b6... Build more of the newer tests we weren't building on VMS. hint: after resolving the conflicts, mark the corrected paths hint: with 'git add &lt;paths&gt;' or 'git rm &lt;paths&gt;' hint: and commit the result with 'git commit' % git status # On branch Branch-0_91 # Changes to be committed: # #modified: </pre> Craig A. Berry 2012-05-22T02:40:58 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14508 <pre>On Sat, 19 May 2012 13:57:28 +0100 Frediano Ziglio &lt;freddy77&lt; at &gt;gmail.com&gt; wrote: I'm still confused because "git branch" and "git describe" say different things: $ pwd /var/releng/freetds/Branch-0_91 $ git branch * Branch-0_91 master $ git describe --tags branch-0_92-54-ga8789bc $ cd ../master $ pwd /var/releng/freetds/master $ git branch * master $ git describe --tags branch-0_92-325-g9a1fdd5 Is that what we want? I use the script below to generate the version. I expect "git describe --tags" and "git branch" to both say something about "0_91" on the release branch and "0_92" on master. If that's not a good assumption, I'll change it. --jkl #! /bin/sh set -e VERSION=$(git describe --tags \ | sed -E 's/^[^-]*-//; s/-g[[:xdigit:]]+//') BRANCH=$(git branch | awk '/\*/ {print $2}') test "${BRANCH}" if [ master = ${BRANCH} ] then VERSION=$(echo $VERSION | awk -F'[_-]' '{print "dev."$1"_"$2"-"$3}') fi VERSION=$(echo $VERSION | sed 's/[_-]/./g') echo $VERSION </pre> James K. Lowden 2012-05-21T18:04:28 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14507 <pre>Hi, I created a new freetds repo at https://gitorious.org/~freddy77/freetds/mars-freetds. No, I'm not mad and it's not a fork. However I don't like to have my personal branches on the official repo. One of the main reason is to share mars branch (actually the only additional branch). Currently all tests passes even with mars code !!! But not all enabling mars... and upper layers do not currently support it and there are no specific tests! So... quite useless branch :) Apart from odbc support (the only library which support it) blob1 test fails with mars enabled due to the fact that if client does not limit packets sending speed server drop connection. I think this is another point to add to the James page on why do not use mars !! The other test that fails is cursor4 due to different protocol for transaction if mars is enabled (perhaps another small point to add to above page). Currently another problem is error reporting. If server drop connection all sessions should receive a network error. Fredia</pre> Frediano Ziglio 2012-05-19T16:53:55 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14506 <pre>According to Frediano Ziglio: Thank you very much! (Open Source is great...;-) \wlang{} </pre> Willi Langenberger 2012-05-19T15:27:57 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14505 <pre>2012/5/18 James K. Lowden &lt;jklowden&lt; at &gt;freetds.org&gt;: Yes, confirmed !! I think that "git push" is enough. I backported the change of memset as a small security issue. Well spot! I noted that you fixed the +1 version issue too. Good! However I found a small issues, 0_91.46 should be 0.91.46. Spec file is updated too. Good! Frediano _______________________________________________ FreeTDS mailing list FreeTDS&lt; at &gt;lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/freetds </pre> Frediano Ziglio 2012-05-19T12:57:28 http://permalink.gmane.org/gmane.comp.db.tds.freetds/14504 <pre>For anyone interested in the git repository, I just pushed my first commit with git push ssh://git&lt; at &gt;gitorious.org/freetds/freetds.git It seemed work. I'm still getting the hang of git. There are two changes: 1. fix code that induces warnings in clang. All innocuous. 2. remove txt2man. All man pages are now in -mdoc format. It was a few hours' work. The man pages now look a little better and we lose one dependency. With a little cleverness, we could have them in PDF format, too. The warnings were mostly about using // as a comment, something I'm guilty of. These became either /**/ or #if 0. The most significant changes are to md4.c and md5.c. Each had a line memset(ctx, 0, sizeof(ctx)); now memset(ctx, 0, sizeof(*ctx)); The line intends to clear memory before returning to prevent sensitive data from remaining in memory. It was clearing sizeof(void*) instead of the whole structure. --jkl </pre> James K. Lowden 2012-05-18T21:50:31 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.db.tds.freetds