The MySQLdb library has CLIENT.FOUND_ROWS = 2. What value ideally it should have ?
I am still now clear why this problem was not coming in the earlier SA version! On 7/31/07, Arun Kumar PG <[EMAIL PROTECTED]> wrote: > > I am using pool.QueuePool for managing connections and this pool is fed > with a creator function which returns an instance of my own custom DBAPI > class (I need this because of some logging stuff that I am doing). This > custom DBAPI class returns a Connection object returned by MySQLdb.connect > . > > >>> The FOUND_ROWS client flag must be enabled on MySQL connections to > make rowcount return what you (and SA) are expecting. > > This has been enabled recently on SA 3.9 ? because the previous version > was working fine. > > > On 7/31/07, jason kirtland <[EMAIL PROTECTED]> wrote: > > > > > > Arun Kumar PG wrote: > > > Looks like the problem is coming because of the fact when we are > > > updating a row in table with the same data the rowcount returned by > > > mysql is 0. Only when there is a change in data the rowcount is > > returned. > > > > Are you creating connections outside of SQLAlchemy? (I seem to recall > > you were using a custom creator function.) The FOUND_ROWS client flag > > must be enabled on MySQL connections to make rowcount return what you > > (and SA) are expecting. > > > > > > > > > > > > > -- > Cheers, > > - A -- Cheers, - A --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
