RE: new configuration settings

Thanks Freddy,

You're absolutely right on all counts.

I was thinking along exactly the same lines.

Our handling of the returned data from sp_executesql was a bit broken as
well, but I've fixed that.

I've been tied up unexpectedly on some important other work for the last few
days, so I haven't finished yet...

Bill

> -----Original Message-----
> From: ZIGLIO Frediano [SMTP:Frediano.Ziglio@xxxxxxxxxxxx]
> Sent: 29 October 2003 15:11
> To:   FreeTDS Development Group
> Subject:      RE: [freetds] new configuration settings
> 
> > 
> > Thanks a lot James,
> > 
> > I'll test it out the disable-iconv stuff on Monday.
> > 
> > fair exchange is no robbery, as they say. I'll submit my 
> > patch early next 
> > week.
> > I got kind of absorbed with getting the 
> > ctlib/unittests/lang_ct_param program 
> > working against SQL Server, as someone has expressed an 
> > interest in getting 
> > that sorted.
> > 
> > Bill
> 
> About lang_ct_param: this test never worked. The simple reason is that
> this function use a Sybase version of TDS_LANGUAGE token. MSSQL support
> language only in language packet so you have to use prepared statement
> to use parameters (or build a string, possible but not good for
> performance). Current code use sp_executesql but is broken. Calling
> sp_executesql is a good solution but require that all parameters have a
> correct name. For example you can call sp_executesql with 
> 
> EXEC sp_executesql, N'insert into test(i) values(@i)', N'@i INT', 123
> 
> If you set parameters without names tds_submit_query_params build a
> parameter string (the N'@i INT' above) without names (N' INT') that's
> wrong... The solution should be parse query string and find parameters
> ('insert into test(i) values(@i)' -> @i) and set in params parameters.
> Also you should skip 'declare @name type' statements...
> 
> freddy77
> _______________________________________________
> FreeTDS mailing list
> FreeTDS@xxxxxxxxxxxxxxxxx
> http://lists.ibiblio.org/mailman/listinfo/freetds