Does the problem occur only with shell? If so, are you doing db.commit() after that statment? This may be a quirk of how sqlite handles transactions? Which OS? Are you sure the behavior changed from 1.61 to 1.62?
On May 11, 9:32 am, Kuba Kucharski <[email protected]> wrote: > > Can you explain better? Do you think this bug in web2py or your code? > > might it be locks on sqlite that I see such things? > I have to work on (semi)-production environment. should I move to > mysql or pgsql now to avoid problems? > my code seems ok.. > > if not.. : > > could you please do: > > db.auth_user[10]=dict(registration_key=' ') > > where '10' is an id of an existing user which have some key there. > > and tell me if it is alright with you how it behaves. just from > console, with python -S app -M. I expect replacement of the > registration_key. What I get is appending new value to previous value > in db. > > -- > Kuba --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
