i committed a fix, i just made the serializer for order creation reentrant, doing a mod if its the primary key (order id ) already exists.
-kapil On Tue, Sep 30, 2008 at 12:38 PM, Horacio Duran <[EMAIL PROTECTED]>wrote: > > Hi I (actually a client) noticed because an error thrown by sqlalchemy > in getpaid.report the following behaviour. > When a user performs the checkout at the last step, when the order is > created, we notify OrderCreation which is good, all subscribers are > triggered and the world is happy but, if the payment processing fails > then when the users goes back and corrects his payment data (suposing > the problem is fixable and can then finish the purchase) the create > notification is triggered again for the same order creating for > instance, an error in getpaid report that tries to create again the > order in the db and fails with a unique constraint violation. > The question is, this should be handled in the order creation code and > rething where to notify create or in the subscribers and make sure > this is not the first time we see create? > I believe the first but would love to hear your opinions. > -- > Perrito > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "getpaid-dev" 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/getpaid-dev?hl=en -~----------~----~----~----~------~----~------~--~---
