> > > Is the concern that the commit operation of the second transaction will > itself raise an exception (at which point, the first transaction has > already been commited)? Aside from that possibility, wouldn't any error > (within the databases or otherwise) simply result in both transactions > being rolled back? I'm not saying this is as good as having everything in > one database, but if you *have to* have two databases, you have to manage > this via the framework/app code somehow. What else would you suggest? >
manage it by hand knowing the possible problems related. I will stay out of that business up until dead, knowing that far more experienced coders (and with far advanced languages) didn't fix the issue in 30 years. Some things we can act on, some things we can improve "magic" behind it because experts know exactly what to do, some other things will be left unimplemented not because we don't want to enhance "framework friendlyness", but because there is simply no fix for it. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
