headers
Iacono, Salvatore (Pfaeffikon | 1 Sep 2011 16:31
Favicon

date and datetime2 support on 7.2?

Hello.
Do you support date and datetime2 sql server 2008 types on release 0.91 with protocol 7.2?
Thanks.
-s

This email has been sent by a member of the Man group (“Man”). Man’s parent company, Man Group plc, is
registered in England and Wales (company number 2921462) at Sugar Quay, Lower Thames Street, London EC3R
6DU, UK.
The contents of this email are for the named addressee(s) only. It contains information which may be
confidential and privileged. If you are not the intended recipient, please notify the sender
immediately, destroy this email and any attachments and do not otherwise disclose or use them. Email
transmission is not a secure method of communication and Man cannot accept responsibility for the
completeness or accuracy of this email or any attachments. Whilst Man makes every effort to keep its
network free from viruses, it does not accept responsibility for any computer virus which might be
transferred by way of this email or any attachments. This email does not constitute a request, offer,
recommendation or solicitation of any kind to buy, subscribe, sell or redeem any investment instruments
or to perform other such transactions of any kind. Man reserves the right to monitor, record and retain all
electronic and telephone communications through its network in accordance with applicable laws and
regulations. --UwQe9f5k7pI3vplngP
_______________________________________________
FreeTDS mailing list
FreeTDS <at> lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds
Permalink | Reply | 1 comment |
headers
Frediano Ziglio | 1 Sep 2011 16:52
Picon

Re: date and datetime2 support on 7.2?

2011/9/1 Iacono, Salvatore (Pfaeffikon) <Salvatore.Iacono <at> man.com>:
> Hello.
> Do you support date and datetime2 sql server 2008 types on release 0.91 with protocol 7.2?
> Thanks.
> -s
>

No, 0.91 support protocol up to 7.2 using ODBC and protocol 7.2 does
not support datetime2.
Current CVS have partial support for these types but is in a real
development stage.

Frediano
Permalink | Reply | 0 comments |
headers
Mike Slifcak | 1 Sep 2011 18:04

feature changes between 0.82 and 0.91

Hi, FreeTDS developers.
Thank you for producing this library.
I'm still somewhat new to the project, but I have not found the information
I'm looking for.  I'll be glad to take directions and pointers that you may offer.

Is there a brief description of the new capabilities for 0.91?
I'm looking particularly for leverage to convince existing 0.82 users to upgrade.

Do the new capabilities require configuration change?  I know of one 'yes' case.

Also, are there any constructs or uses which should be considered 'old' or deprecated,
which your team plans to obsolete in upcoming releases?  Something akin to a migration 
guide, if that makes sense.

Thank you,
-Mike Slifcak
Permalink | Reply | 4 comments |
headers
Frediano Ziglio | 3 Sep 2011 11:00
Picon

Re: feature changes between 0.82 and 0.91

Il giorno gio, 01/09/2011 alle 12.04 -0400, Mike Slifcak ha scritto:
> Hi, FreeTDS developers.
> Thank you for producing this library.
> I'm still somewhat new to the project, but I have not found the information
> I'm looking for.  I'll be glad to take directions and pointers that you may offer.
> 
> Is there a brief description of the new capabilities for 0.91?
> I'm looking particularly for leverage to convince existing 0.82 users to upgrade.
> 

See http://lists.ibiblio.org/pipermail/freetds/2011q3/027244.html

> Do the new capabilities require configuration change?  I know of one 'yes' case.
> 

?? which one ??
Consider that protocol 8.0 is detected as 7.1 by FreeTDS 0.91

> Also, are there any constructs or uses which should be considered 'old' or deprecated,
> which your team plans to obsolete in upcoming releases?  Something akin to a migration 
> guide, if that makes sense.
> 
> 
> Thank you,
> -Mike Slifcak

Which library are you using. Probably writetext and related are
affected.

Frediano
(Continue reading)

Permalink | Reply | 1 comment |
headers
Frediano Ziglio | 3 Sep 2011 11:20
Picon

Thread improvements on CVS

Hi,
  for who is following CVS code you should have noted some changes
during last days. I finally manage to find some time to sort out and fix
my patches and work for thread and cancellation.

For libTDS there is now a TDSSOCKET->wire_mtx mutex which serialize
access to same connection (required). Currently this mutex is
automatically locked and unlocked on state changes. It does not
currently prevent memory races accessing TDSSOCKET outside
sending/receiving data.

For ODBC there are mutex for every structure (connection, statement,
environment and descriptors) locked and unlocked for every function.

Another change is cancellation. Currently a socketpair is used to advise
sending thread of a pending cancellation. This way you can safely cancel
from signal (as ctlib/dblib specification) and from another thread (as
ODBC specification) without memory races problems.

All these changes minimally affect token.c and query.c

Frediano
Permalink | Reply | 0 comments |
headers
Mike Slifcak | 3 Sep 2011 13:29

Re: feature changes between 0.82 and 0.91

Thank you.  I recall seeing the announcement.  I was hoping for something more detailed, 
without staring down the sources.

'yes' case is realm, the one we collaborated.

Thanks for the note about writetext.

Regards,
-Mike Slifcak

Frediano Ziglio wrote:
> Il giorno gio, 01/09/2011 alle 12.04 -0400, Mike Slifcak ha scritto:
>> Hi, FreeTDS developers.
>> Thank you for producing this library.
>> I'm still somewhat new to the project, but I have not found the information
>> I'm looking for.  I'll be glad to take directions and pointers that you may offer.
>>
>> Is there a brief description of the new capabilities for 0.91?
>> I'm looking particularly for leverage to convince existing 0.82 users to upgrade.
>>
> 
> See http://lists.ibiblio.org/pipermail/freetds/2011q3/027244.html
> 
>> Do the new capabilities require configuration change?  I know of one 'yes' case.
>>
> 
> ?? which one ??
> Consider that protocol 8.0 is detected as 7.1 by FreeTDS 0.91
> 
>> Also, are there any constructs or uses which should be considered 'old' or deprecated,
(Continue reading)

Permalink | Reply | 0 comments |
headers
James K. Lowden | 3 Sep 2011 16:29

Re: FreeTDS 0.9.1 problem build on Solaris 10x86

On Wed, 31 Aug 2011 14:41:25 -0400
Todd Szymanski <toddzman <at> gmail.com> wrote:

> Just wanted to pass along that I was unable to successfully do a 'make
> install' on 0.9.1.  It seems like it worked, but it doesn't when you
> go to use it.  It looks like the install-sh that is included in the
> distribution does not handle multiple files on one command line (I've
> only tried it on Solaris).

Your experience isn't typical, to say the least.  I wonder: does
Solaris have an install(1) on the PATH?  

$ file $(which install)
/usr/bin/install: ELF 64-bit LSB executable, x86-64 ....

It seems you *did* find a bug, albeit one masked on machines with a
built-in install utility.  The FreeTDS distribution tarball includes
an install script, but configuration.ac -- from which the configure
script is generated by autoconf -- does not reference it as
AC_PROG_INSTALL.  I would think configure, finding no built-in install
utility and having not been directed to use another, would simply
fail.  Apparently, it uses the one it finds in the current working
directory, if extant.  And fails silently.  :-/

I'm inclined to simply remove install-sh from the FreeTDS
distribution.  In 2011, machines without an install utility must be
very rare, and a message like "sh: install: command not found" would be
better than pretending to work.  

That leaves it to the sysadmin to provide an install utility.  The
(Continue reading)

Permalink | Reply | 3 comments |
headers
Mike Slifcak | 3 Sep 2011 16:55

Re: FreeTDS 0.9.1 problem build on Solaris 10x86

autogen driving autoconf/automake is viable.  I know that Net-SNMP uses autoconf on 
Solaris with no issues.
-Mike Slifcak

James K. Lowden wrote:
> On Wed, 31 Aug 2011 14:41:25 -0400
> Todd Szymanski <toddzman <at> gmail.com> wrote:
> 
>> Just wanted to pass along that I was unable to successfully do a 'make
>> install' on 0.9.1.  It seems like it worked, but it doesn't when you
>> go to use it.  It looks like the install-sh that is included in the
>> distribution does not handle multiple files on one command line (I've
>> only tried it on Solaris).
> 
> Your experience isn't typical, to say the least.  I wonder: does
> Solaris have an install(1) on the PATH?  
> 
> $ file $(which install)
> /usr/bin/install: ELF 64-bit LSB executable, x86-64 ....
> 
> It seems you *did* find a bug, albeit one masked on machines with a
> built-in install utility.  The FreeTDS distribution tarball includes
> an install script, but configuration.ac -- from which the configure
> script is generated by autoconf -- does not reference it as
> AC_PROG_INSTALL.  I would think configure, finding no built-in install
> utility and having not been directed to use another, would simply
> fail.  Apparently, it uses the one it finds in the current working
> directory, if extant.  And fails silently.  :-/
> 
> I'm inclined to simply remove install-sh from the FreeTDS
(Continue reading)

Permalink | Reply | 2 comments |
headers
Ken Collins | 4 Sep 2011 04:29
Gravatar

Cannot Use DBVERSION_72 With DBLIB In 0.91 Release


I just recently found out that I have been testing TinyTDS using DBVERSION_71/DBVERSION_80 on all my
databases versions from 2000-2008 & Azure and I decided I needed to try out the DBVERSION_72 since my main
focus is on 2005 and up. I have run into the following issues:

1) I can not configure FreeTDS --with-tdsver="7.2". Is this an oversight?

2) I found out that dbsetversion is basically a no-op that sets a global. However, it has not been updated
with DBVERSION_72 and was throwing a bunch of "FreeTDS: db-lib: exiting because client error handler
returned INT_EXIT for msgno 20206" which was misleading. Should it be patched like so?

--- dblib.c
+++ (clipboard)
 <at>  <at>  -5801,8 +5801,8  <at>  <at> 
 	case DBVERSION_42:
 	case DBVERSION_46:
 	case DBVERSION_100:
-	case DBVERSION_70:
-	case DBVERSION_80:
+	case DBVERSION_71:
+	case DBVERSION_72:
 		g_dblib_version = version;
 		return SUCCEED;
 	default:

3) Even if I do not use dbsetversion and avoid the problem above and instead rely on
dbsetlversion(DBVERSION_72), I can not get a connection. The message is "TDS version downgraded to
7.1!" and it is driving me nuts. I consistently get this error weather I use the TDSVER environment
variable, freetds.conf setting, etc. Any insight?
(Continue reading)

Permalink | Reply | 10 comments |
headers
James K. Lowden | 4 Sep 2011 14:43

Re: feature changes between 0.82 and 0.91

On Thu, 01 Sep 2011 12:04:22 -0400
Mike Slifcak <slif <at> bellsouth.net> wrote:

> Is there a brief description of the new capabilities for 0.91?
> I'm looking particularly for leverage to convince existing 0.82 users
> to upgrade.
On 3 Sep 2011 Mike Slifcak <slif <at> bellsouth.net> wrote:
> I recall seeing the announcement.  I was hoping for something more
> detailed

To me, the announcement is a list of things you can look forward to if
you use 0.91.  It is derived from ChangeLog, details therein.  

The best reason to upgrade is support, such as it is.  We provide point
releases -- bug fixes -- as and when problems are reported.  If nothing
else, by using 0.91 you'll be using the most popular version, meaning
any problems you encounter have the greatest likelihood of having been
seen/fixed/worked around by others.  

Problems with prior releases won't see any further attention from the
developers.  When someone reports a problem with an earlier version
since fixed, we always advise upgrading.  

> Also, are there any constructs or uses which should be considered
> 'old' or deprecated, which your team plans to obsolete in upcoming
> releases?  Something akin to a migration guide....

Contrary to what you might expect, No.  The APIs that FreeTDS
implements were first specified over 20 years ago and haven't changed
significantly since the mid-1990s.
(Continue reading)

Permalink | Reply | 1 comment |

Gmane