FreeTDS Development Group

["Thompson, Bill D (London)" <bill_d_thompson AT ml.com>]

Hi Vadym,

Without answering your question, one piece of advice...

If at all possible, I would build your libdbi api on top of one of the 
existing api's - dblib ctlib or odbc.
I'd be interested to know what you want to do that you feel these API's 
cannot provide...

The tds layer is really intended to be internal to freetds itself.
Very often, we find it necessary to alter the specification and/or behaviour 
of the libtds functions.
You will, therefore, be making a future problem for yourself by basing your 
code on libtds.

On top of that, the dblib, ctlib and odbc api's are well documented publicly, 
providing you with a good description of expected behaviours on which to base 
your libdbi code.
We maintain the documented behaviour of these API's under all circumstances.

HTH,

Bill

-----Original Message-----
From: freetds-bounces AT lists.ibiblio.org 
[mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of Vadym Kononenko
Sent: 18 August 2005 12:29
To: FreeTDS Development Group
Subject: [freetds] libdbi - freetds driver


Hi, all.
I'm working on new libdbi driver to adapt freetds library.

On this moment I have some problems using freetds (tds layer), listed
below. Can anybody hint me where to get related info?

1) How can I check reply code from database server?
Now, in most cases, I receive result type TDS_DONE from 
"tds_process_row_tokens()"
call, so it isn't depend on an error messages from database server.

2) After the "tds_process_row_tokens()" call I parsing received rows.
The data of text fields ("tds_socket->res_info->current_row") are
mixed from current and previous rows (looks like dirty buffer).

 For example:
   First value: "Firstlinedata"
   Next Value: "Nextdata"
   Showed: "Nextdataedata"
-- 
Best regards.
Vadym Kononenko.
Kyiv, Ukraine
_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds
--------------------------------------------------------

If you are not an intended recipient of this e-mail, please notify the 
sender, delete it and do not read, act upon, print, disclose, copy, retain or 
redistribute it. Click here for important additional terms relating to this 
e-mail.     http://www.ml.com/email_terms/
--------------------------------------------------------