On 13-2-2012 16:33, Dmitry Yemanov wrote:
* Is 0x20 (space) the right pad char for connection characterset NONE?
Yes.
When sending a CHAR CHARACTER SET OCTETS field, I assume that it should
be padded with 0x00, right?
Mark
--
Mark Rotteveel
On 18-2-2012 22:38, Dmitry Yemanov wrote:
15.02.2012 20:01, Mark Rotteveel wrote:
Does SQL_VARYING require the sqllen to be updated as well, or can that
be left as it was originally set by isc_dsql_describe_bind?
I'd say it should correspond to the real data. You're not required to
use
15.02.2012 20:01, Mark Rotteveel wrote:
Does SQL_VARYING require the sqllen to be updated as well, or can that
be left as it was originally set by isc_dsql_describe_bind?
I'd say it should correspond to the real data. You're not required to
use isc_dsql_describe_bind(), after all.
Dmitry
On 13-2-2012 16:33, Dmitry Yemanov wrote:
* Is the size being allocated to data for SQL_VARYING right, shouldn't
the actual size of the byteArray[1] + 3 (or 2) be sufficient instead of
sqllen + 3 (especially for UTF8 and for strings shorter than the maximum
size this is larger than necessary)
11.02.2012 20:49, Mark Rotteveel wrote:
* Is the size being allocated for SQL_TEXT right? It is allocating
sqllen + 1 and null-terminating it, while looking at the Interbase 6
ApiGuide they are always allocating sqllen and not null-terminating
You don't have to null-terminate it, sqllen is
On 13-02-2012 13:33, Dmitry Yemanov wrote:
* For all datatypes other than SQL_VARYING, it is first storing
byteArray size and then overwriting that with the byteArray, so actually
storing that size first is unnecessary, right?
I'm not sure I understand you here.
* Is 0x20 (space) the
On 11-2-2012 17:49, Mark Rotteveel wrote:
On 11-2-2012 16:03, Mark Rotteveel wrote:
And just after I sent my mail I thought of a potential cause which I am
now investigating. It looks like the XSQLVAR sqllen field 4, while the
data array was only 1 entry long. Reducing the sqllen to the actual
The related issue CORE-3701 can be closed (I don't have the rights to do
that).
Mark
--
Mark Rotteveel
--
Virtualization Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud
On 11-2-2012 15:54, Mark Rotteveel wrote:
I am looking for the cause of CORE-3701 / JDBC-233, but I can't identify
the problem.
The problem is this: When using Jaybird native (using fbclient 2.5.1)
the parametrized insert of a single character into a CHAR(1) column
fails with error:
On 11-2-2012 16:03, Mark Rotteveel wrote:
And just after I sent my mail I thought of a potential cause which I am
now investigating. It looks like the XSQLVAR sqllen field 4, while the
data array was only 1 entry long. Reducing the sqllen to the actual
length of the array *or* padding the
10 matches
Mail list logo