FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> -----Original Message-----
> From: Thompson, Bill D (London) [mailto:ThompBil AT exchange.uk.ml.com]
> Sent: January 29, 2003 2:15 AM
> 
> 1) I have recently finished some enhancements to the bcp 
> functionality, and
> these are ready to submit to you. I've added support for 
> text/image columns
> on SQL server (both in and out), made some small performance 
> enhancements,
> and also added more flesh to the "error file" handling on 
> freebcp. I doubt
> anyone's really desperate for these enhancements, but they 
> are "nice to
> haves". The code changes are non-intrusive on the rest of the 
> code, so I am
> pretty confident they would not disrupt an orderly release of 
> 0.61 if anyone wants them included. If you want them, just shout.

Hi Bill, 

As big a fan as I am of bcp and the work you're doing, I think it would be
better to include everything you mentioned in 0.62.  What's in CVS now
hasn't changed much except for bugfixes in the last 4 weeks.  Practically
every problem mentioned on the list is answered by "get the latest snapshot"
(except the "look at the log" answers).  I really think it's time.  

Regarding bcp, are you working on bcp for ct-lib?  If not, I think I will.  

What I would like from you if you wouldn't mind is an updated TODO
reflecting your plans for 0.62.  If you'd "pull up" the items that you think
should go in the next release, that would give 0.61 users a clearer idea
where we're heading.  

> a) text/image type handling. I've finished ct_get_data() and 
> ct_data_info(),
> I'm working on ct_send_data(). Should be finished this week.
> 
> b) server-side cursor support (ct_cursor()). I'm busy writing a
> specification for this work at the moment, and hope to get it 
> kicked off next week. 

Microsoft servers only, or TDS 5, too?  
> 
> c) rpc calls - migrating Freddy's good work into ct-library - 
> will include beefed up ct_param() and ct_setparam()
> 
> and after that, I'm planning for array binding and ct_diag() support.
> 
> Of course, some of this is likely to be quite intrusive on 
> the core code, so
> I wouldn't want it to go into 0.61. However, I would like it 
> to be included
> in an official release as soon as it is stable. So I guess 
> I'm asking us to look ahead to 0.62 in the not too distant...

This is very encouraging.  Are you thinking more like March or June?  

Not to be a noodge, but any progress on the CVS front?  Are you at least
able to keep your workfiles synchronized with HEAD?  

Looking forward to your stuff.  

Regards, 

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.