Re: Using DBLIB With Azure

2011/3/27 James K. Lowden <[email protected]>:
> On Sun, 27 Mar 2011 20:38:05 -0400
>
> The ablility to set defaults in
> freetds.conf can be useful, I agree.  By the same token, for sqsh to
> implement its -D dbname option in an Azure database, ct-lib too will
> need the ability to set the database name in the login packet.
>

ct-lib or we punt to the freetds.conf, in which case sqsh et al. just
continue to work without modification on Azure.

>> dblib is not dead, just the organization in charge of extending it has
>> changed.
>
> Hear, hear, comrade!
>
> Just to re-iterate, a TDS 5.0 login packet has no dbname field; it's a
> TDS 7+ feature.  Microsoft added the ability to set that field to
> ODBC.  They never upgraded their db-lib beyond TDS 4.2, and hence never
> needed extend db-lib in that way.
>
> The login packet also has the 0x40 option to require access to the
> database to be permitted for the login to be accepted.  db-lib has no
> way to set that bit on or off at present.
>

Yes, DBSETLOPTION() is one of my pending extensions.  I need it just
for using the ODBC flag in a dblib program myself, but it's a more
general facility.

> Regards,
>
> --jkl
> _______________________________________________
> FreeTDS mailing list
> [email protected]
> http://lists.ibiblio.org/mailman/listinfo/freetds
>