Re: weirds problems after upgrade from 7.5.00.18 to 7.5.00.19

Dear Dittmar
with the following patch in the python module sapdb.dbapi it is possible 
to use again the fetchall method in the cursor class. I have no clue how 
to fix the fetchone and fetchmany methods

-------in class cursor-----------------------------
    def __fetchall (self):
        cursor = self.__getCursor ()
## --------start new code-------------------
        cursor.first()
        result = [row for row in cursor]
## ----------end new code-------------------
## --------start old code-------------------
##        result = []
##        while 1:
##            row = self.nextFromCursor (cursor)
##            if not row:
##                break
##            result.append (row)
## ---------end old code--------------------
        return result
--------------------------------------------------

There seems to be an important problem with the setTranslation method. 
My implementation of the mapping from Timestamp and Date columns to 
datetime.datetime and datetime.date objects has broken and there is no 
translation anymore, just plain strings instead of datetime objects.

regards
Gottfried Stauffenberg


Daniel Dittmar wrote:
> Jean-Michel OLTRA wrote:
>
> > * on PROD instance, the first insert is performed and the session 
> > commited
> >   after the second one.
> >   There is no error but the second phase seems to have been skipped
> >   (no inserts). Remember, I work with the same scripts and dbproc.
> > # on both instances, ireport cannot find any row by pk on the first table
> >   wrote by script one, but can find rows with another column in the 
> > query.
> >
> >   [22:38]jm@espinasse > ireport -d TEST
> >   SAP DB Terminal Report 0.3.3
> >   Type 'help' for help.
> >   An empty line repeats the last command
> >   ==> select * FROM FLUXFINANCIER where NOPIECE=696
> >   
> > |NOPIECE|NOFACTURE|DATEFACTURE|IDETABLISSEMENT|DATEREGLEMENT|IDMODEREGLEMENT|NOCOMPTE| 
> >
> >   
> > +-------+---------+-----------+---------------+-------------+---------------+--------+ 
> >
> >   <<<End of Cursor>>>
> >   ==> select * FROM FLUXFINANCIER where NOFACTURE='retro-20041122'
> >   
> > |NOPIECE|NOFACTURE|DATEFACTURE|IDETABLISSEMENT|DATEREGLEMENT|IDMODEREGLEMENT|NOCOMPTE| 
> >
> >   
> > +-------+---------+-----------+---------------+-------------+---------------+--------+ 
> >
> >   |696|retro-20041122|20041122|3409-001|?|?|?|
> >   ==> Q
>
>
> There is a bug with this kernel version where some some SELECTs don't 
> seem to find anything. This seems to occur only with the Python driver 
> as rows from cursors are read using FETCH RELATIVE and not FETCH NEXT as 
> most of the other interfaces do. It seems to occur only when rows a 
> qualified by a key column. This will be fixed in 7.5.00.21. You can work 
> around this problem by issuing a resultset.first () before the first 
> .next ().
>
> Daniel Dittmar

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx