I update myself :-)
MS states in the docu:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms710188(v=vs.85).aspx
SQLDescribeParam returns the description of a parameter marker associated
with a prepared SQL statement. This information is also available in the
fields of the IPD.
That mea
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 Wu
Dear all,
Apparently, my first post on this subject didn't arrive in the list. So I try
again.
I assumed, that SQLGetDescXXX functions are OBBC 3 replacements of i.e.
SQLDescribeParam. Is this right, or, in ODBC 3 SQLDescribeParam is the right
way to get parameter information on a prepared stateme
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
OK
~
Tiesheng Wu
Computer Manager
Wolfson Institute of Preventive Medicine
Queen Mary, University of London
Charterhouse Square
London EC1M 6BQ
Tel: 020 7882 6285
Fax: 020 7882 6270
Email: t...@qmul.ac.uk
Web: http://www.wolfson.qmul.ac.uk/
-Original Message-
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
