Subject | Re: [ib-support] Sqlda mispraes or data corruption ? |
---|---|
Author | Paul Reeves |
Post date | 2003-04-04T14:31:46Z |
[detailed explanation of problem snipped]
As you seem to be getting on so well (doing private builds of Fb 1.0,
OdbcJdbc driver etc) I'd recommend taking a look at gpre to use as a
debugging tool. It allows you write scripts that combine fairly simple C
with more or less standard SQL. It converts the SQL into raw api calls.
From there you just compile the output as a normal C program and step
through it in the debugger.
You will find some examples to use as a starting point in the (wait for
it) examples directory. Take a look at the dyn*.e files - dyn4.e in
particular, which has a parameterised update statement. It should be
simple enough to have a test app up and running in an hour or so.
The idea I'm suggesting is basically to see if you can reproduce the
problem with a gpre based program. If so, then it is likely to a
Firebird problem. If not it is likely be an Odbc driver problem. It will
certainly remove most of the intermediate layers that are getting in the
way.
You can pick up a gpre manual here:
http://www.ibphoenix.com/downloads/60EmbedSQL.zip
Gpre hasn't changed in recent years so any IB manual for gpre will do.
Paul
--
Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase
As you seem to be getting on so well (doing private builds of Fb 1.0,
OdbcJdbc driver etc) I'd recommend taking a look at gpre to use as a
debugging tool. It allows you write scripts that combine fairly simple C
with more or less standard SQL. It converts the SQL into raw api calls.
From there you just compile the output as a normal C program and step
through it in the debugger.
You will find some examples to use as a starting point in the (wait for
it) examples directory. Take a look at the dyn*.e files - dyn4.e in
particular, which has a parameterised update statement. It should be
simple enough to have a test app up and running in an hour or so.
The idea I'm suggesting is basically to see if you can reproduce the
problem with a gpre based program. If so, then it is likely to a
Firebird problem. If not it is likely be an Odbc driver problem. It will
certainly remove most of the intermediate layers that are getting in the
way.
You can pick up a gpre manual here:
http://www.ibphoenix.com/downloads/60EmbedSQL.zip
Gpre hasn't changed in recent years so any IB manual for gpre will do.
Paul
--
Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase