Re: Are unittests expected to fail?

Hi Freddy...

Thanks for responding...

>You are using TDS 4.2. Try with an higher TDS version. Usually I try
>with unixODBC. Current results (TDS5+, unixODBC) should be
> - with GNU iconv + single-byte

Ok - point number one I was using the wrong TDS version - but this
doesn't affect what I see with the ODBC unit-tests.

Still 6 failures as before with unixODBC.
(As for iconv - I'm not using GNU, just what comes with FreeTDS:

- connect - succeeds with several connection strings, but fails on the
    old version, due to my inability to configure odbcinst.ini properly.
    Doesn't affect ability of other tests to connect. So probably not an
    issue.
- funccall - don't know what's wrong here. Output parameters?
- moreandcount - odd. Returned 0 columns instead of 1.
- params - Don't know. Does output parameter support work?
- transaction - Don't know why commit failed.
- type - Well this is quite possibly down to iconv

I see that the last 3 are failures you listed. So the main mystery is over
funccall and moreandcount - I guess. Any ideas?

I've attached the output from make check, in case you
or anyone else can be bothered.

Cheers,

David

makecheckout.txt
Description: Text document

_______________________________________________
FreeTDS mailing list
FreeTDS@xxxxxxxxxxxxxxxxx
http://lists.ibiblio.org/mailman/listinfo/freetds