FreeTDS Development Group

[Dave Dumaresq <ddumaresq AT bccampus.ca>]

Hi, yes it was a bug fixed in last night's snapshot. Here is the output:

$ ./osql -S dsn_myvista -U sa -P 1234
checking shared odbc libraries linked to isql for default directories...
        trying /tmp ... no
        trying /sql ... no
        trying /tmp ... no
        trying /sql ... no
        trying /usr ... no
        trying /loc ... no
        trying /tmp/sql.log ... no
        trying /home ... no
        trying /.odbc.ini ... no
        trying /usr/local/unixODBC/etc ... OK
checking odbc.ini files
        reading /home/ddumaresq/.odbc.ini
[dsn_myvista] not found in /home/ddumaresq/.odbc.ini
        reading /usr/local/unixODBC/etc/odbc.ini
[dsn_myvista] found in /usr/local/unixODBC/etc/odbc.ini
found this section:
        [dsn_myvista]
        #Driver=FreeTDS
        Servername=freetds_dsn_myvista
        Driver=/usr/local/freetds/lib/libtdsodbc.so
        Description=My local vista box containing ACP
        User=sa
        Password=1234
        Database=ldap
        
looking for driver for DSN [dsn_myvista] in /usr/local/unixODBC/etc/ 
odbc.ini
  found driver line: "     Driver=/usr/local/freetds/lib/libtdsodbc.so"
  driver "/usr/local/freetds/lib/libtdsodbc.so" found for  
[dsn_myvista] in odbc.ini
found driver named "/usr/local/freetds/lib/libtdsodbc.so"
/usr/local/freetds/lib/libtdsodbc.so is an executable file
Using ODBC-Combined strategy
DSN [dsn_myvista] has servername "" (from /usr/local/unixODBC/etc/ 
odbc.ini)

Right now, I have my server defined in freetds.conf  
(Servername=freetds_dsn_myvista), does the above line indicate it's  
expecting the server definition in odbc.ini?

Dave

On 6-May-11, at 7:37 AM, jklowden AT schemamania.org wrote:

> On Thu, May 05, 2011 at 01:18:10PM -0700, Dave Dumaresq wrote:
> > I have solved my connection problem -- I had left the freetds.conf
> > servername out of my odbci.ini. Still the osql driver line incomplete
> > issue is there. A bug?
>
> Hi Dave,
>
> Thanks for the problem report.  It could be a bug; it might already  
> be solved.
> The current version of osql prints a line
>
>         found driver line: \"${DRIVER_LINE}\"
>         
> that doesn't appear in your log.
>
> If you want to help solve it, please download the latest version of  
> the script
> from CVS or unpack it from last night's tarball.  If that version
> fails, run it as
>
>         sh -x /bath/to/osql
>         
> and post the results here.  (Patches welcome too!)
>
> It might be fooled by the uppercase in "Driver" or the lack of spaces
> surrounding the "=" sign.  But I looked it over and didn't see  
> anything wrong,
> so I thought I'd ask you to test it directly, if you would.
>
> Regards,
>
> --jkl
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds

--
Dave Dumaresq
Technical Analyst - BCcampus
200 - 555 Seymour St, Vancouver BC
Phone: 604-412-7738