Hello,
In the past, I could login and use the firebird tracker w/o problem.
Today I wanted to login again, and the system told me, that I may not login
(no permission). Thought I used the wrong pwd, tried others, w/o success.
Clicked on "forgot pwd", entered email, and then the system showed an
exc
On 07.02.2013 12:14:06, "Jojakim" wrote:
> ...But in the case of BLOB,
> subtype is not used to indicate the specified BLOB SUB_TYPE ...
Sorry, there is a typo: Must be:
But in the case of BLOB, subtype _is_ used to indicate the specifi
Dear specialists,
I need your advice for the following problem:
(see also http://tracker.firebirdsql.org/browse/ODBC-161)
I bound a BLOB SUB_TYPE 1 CHARACHTER SET UTF8 field to SQL_C_WCHAR /
SQL_LONGVARCHAR via SQLBindParameter on an insert operation. Then encountered
problems when using SQLPutDa
means, that the driver's SQLGetDescXXX function is buggy, at least for
the IPD case.
--
Joja
On 04.02.2013 12:31:49, "Jojakim" wrote:
> Dear all,
> Apparently, my first post on this subject didn't arrive in the list. So I
> try again.
>
> I assumed, that
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
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?
>
> IM
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
