Hello,
I am getting errors in queries on a MySQL 5.027 database using zmysqlda
2.0.9b3 and mysql-python 1.2.1 with Zope 2.10.2.
The errors occured the next day after setting the whole thing up and
while at first it was working all right. The event log tells me that
MySQL has 'gone away', it proba
--On 20. März 2007 09:18:19 +0100 [EMAIL PROTECTED] wrote:
Hello,
I am getting errors in queries on a MySQL 5.027 database using zmysqlda
2.0.9b3 and mysql-python 1.2.1 with Zope 2.10.2.
The errors occured the next day after setting the whole thing up and
while at first it was working all ri
Thanks, Andreas, I will look at the mysql log files.
I was also thinking about incompatibilities between the zmysql database
adapter and the last Zope version. I have used the same setup with Zope
2.9.2 before without this problem.
Henk
Op Di, 20 maart, 2007 9:20 am schreef Andreas Jung:
>
>
>
To give an update:
To run a stored procedure which returns a ref cursor, I tried:
c1 = db.cursor()
c2 = db.cursor()
sql = "storedProcedureName(:inparam1, :inparam2, etccc, :outparam)"
options = (inparam1, inparam2, et, c2)
c1.execute(sql, options)
As recommended below.
This did not work.
Howev
You have a point Maciej - but I got used to DCOracle2 and so far it has
performed quite well. I link it with Oracle lib32 libraries, but use it
with ora lib 64-bit libraries in the path. So far, there has been no
issues I am aware of. The only thing that came up recently is how to
use it with a
If I recall, DCOracle2 returns an array of the OUT parameters from
invoking a stored procedure, so your invocation would be more like
c2 = c1.sp1(in1, in2, in3, in4) and you wouldn't pass in ref_cur
but its been a while since I reviewed the code. I know ref cursors
used to work...
On Mar
Chances are good that the C code that is trying to construct the
timestamp doesn't know how to convert it...
A quick peek into the source code hints the code doesn't have a type
converter for SQLT_TIMESTAMP, although there is a converter for
SQLT_DAT (date).
Putting a converter into the C
> This was causing a segmentation fault on a Sun Solaris box.
> On Windows, I got an actual error message. While fetching, the cursor
> has a field of ora datatype TimeStamp. This was crashing DCOracle2. a
> to_char solved the issue.
> I am using DCOracle2 and Oracle 10 on Solaris (and Windows
