[sqlalchemy] Re: fetchmany() vs sqlite

2007-03-08 Thread Lele Gaifax
Michael Bayer wrote: FB - ?? I confirm that the kinterbasdb follows the DBAPI here, and thus its Cursor.fetchmany() accepts an optional positional argument for the size. ciao, lele. --~--~-~--~~~---~--~~ You received this message because you are subscribed

[sqlalchemy] Re: fetchmany() vs sqlite

2007-03-08 Thread Lele Gaifax
Michael Bayer wrote: FB - ?? For what is worth, it actually accepts either a single positional argument or a `size` keyword argument. ciao, lele. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy

[sqlalchemy] Re: fetchmany() vs sqlite

2007-03-07 Thread Tim Golden
On Mar 6, 11:37 pm, Michael Bayer [EMAIL PROTECTED] wrote: OK who can try Mysql, MS-SQL, Oracle, Firebird for me ? while it seems like it should work positionally for all of them, it sort of seems it should work keyword-wise as well if the DBAPI authors actually read the spec they were

[sqlalchemy] Re: fetchmany() vs sqlite

2007-03-07 Thread Michael Bayer
OK its looking like having it as positional might just be what they all commonly had in mind... On Mar 7, 2007, at 5:15 AM, Tim Golden wrote: On Mar 6, 11:37 pm, Michael Bayer [EMAIL PROTECTED] wrote: OK who can try Mysql, MS-SQL, Oracle, Firebird for me ? while it seems like it should

[sqlalchemy] Re: fetchmany() vs sqlite

2007-03-07 Thread JP
I filed a ticket with a patch: http://www.sqlalchemy.org/trac/ticket/505 JP On Mar 7, 11:17 am, Michael Bayer [EMAIL PROTECTED] wrote: OK its looking like having it as positional might just be what they all commonly had in mind... On Mar 7, 2007, at 5:15 AM, Tim Golden wrote: On Mar