Daniel,
Thank You, that worked fine.
In case anyone else can find this useful, The final working code for converting from a
long to a varchar is:
import sys
import sapdb.sql
session=sapdb.sql.connect("DBA","PWD","DBName","ServerName")
cursor=session.sql("select ID,Comments from table1")
cur
> > Note that if you use ROWNO, then a following ORDER BY clause will sort
> > only
> > the records until the limit of ROWNO is reached. It says so in the
manual
> > at
> > least, I haven't tried it... Makes the feature a bit useless IMO...
You
> > can
> > set MaxDB to parse in Oracle mode
I've been able to reproduce the error, but I'm still searching for the cause.
You can work around the problem through
cursor.setFetchSize (1)
The cursor will then get only one row per network request. This is slower, but it
doesn't seem to confuse the python driver as much when LONGs are part of
Hallo Uwe!
Thanks for the very fast answer! It works fine now.
Regards,
Martin
Hahn, Uwe wrote:
db_activate recover
is the command you are looking for.
regards,
Uwe
-Original Message-
From: Martin Lackner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 27, 2004 1:00 PM
To: [EMAIL PROTE
db_activate recover
is the command you are looking for.
regards,
Uwe
>-Original Message-
>From: Martin Lackner [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, July 27, 2004 1:00 PM
>To: [EMAIL PROTECTED]
>Subject: Recover an earlier status of the database instance
>
>
>Hallo!
>
>In the doc
Hallo!
In the documentation
"How to Backup and Recover MaxDB with the Database Manager CLI"
http://dev.mysql.com/doc/maxdb/pdf/backrec_eng.pdf
on the last page it is described how to recover an earlier status of the
database instance. But for 7.5 this does not work anymore because the line
util
User FB24_KAT_DE connected to database KNAUF_DB on local host.
TABLELOAD USER DATA INSTREAM FILE 'FB24_KAT'
-25801
Internal error [vls28_TLoad.cpp, 1566, -25801]; contact technical
support
Successfully executed
I have also find in the file loader.prt:
// M START 20040727 0011092
J S wrote:
>
> Hi,
>
> Can anyone help me with the problem below please? I'm using
> mysql-max-4.0.20-ibm-aix4.3.3.0-powerpc.
Oops, sorry, but this is the wrong list for your problem.
Here is the list for MaxDB usage, not for MySQL-Max.
Naming confuses, I agree, but there is only little/no chan
