Sorry, I sent out the previous email by mistake.
-Original Message-
From: Tiesheng Wu [mailto:t...@qmul.ac.uk]
Sent: 04 February 2013 11:01
To: firebird-odbc-devel@lists.sourceforge.net
Subject: Re: [Firebird-odbc-devel] SQLxxxW functions
OK
~
Tiesheng
04.02.2013 12:10, Jojakim wrote:
> But my question was, how these fields are (or should be) used in the driver
> sources. Is this like the standard, or do they have some internal meanings or
> special treatments in special cases. And how should they be set up from the
> FBs meta data info.
It d
Hi,
The issues with these functions are unknown.
Add information how to reproduce issues into the Tracker -
http://tracker.firebirdsql.org/browse/ODBC
On 04.02.2013 14:25, Jojakim wrote:
> Dear all - and especially the maintainer,
>
> I try to use the SQLxxxW functions and SQL_C_WCHAR type for
On 04.02.2013 11:56:58, Dimitry Sibiryakov wrote:
> 04.02.2013 11:25, Jojakim wrote:
>> What is the experts opinion on how octetLength, length, precision, scale and
>> displaySize should be handled, and what should they containg depending on the
>> FB data type?
>
> IMHO, standard description is q
-
From: Dimitry Sibiryakov [mailto:s...@ibphoenix.com]
Sent: 04 February 2013 10:57
To: firebird-odbc-devel@lists.sourceforge.net
Subject: Re: [Firebird-odbc-devel] SQLxxxW functions
04.02.2013 11:25, Jojakim wrote:
> What is the experts opinion on how octetLength, length, precision,
>
04.02.2013 11:25, Jojakim wrote:
> What is the experts opinion on how octetLength, length, precision, scale and
> displaySize should be handled, and what should they containg depending on the
> FB data type?
IMHO, standard description is quite clear. For string data length and
display size are
Dear all - and especially the maintainer,
I try to use the SQLxxxW functions and SQL_C_WCHAR type for accissing the
driver and discovered problems with string data trucation etc.
Are there knows issues with these functions?
As, in the past, I already fixed minor problems in the driver, I wanted
