On Jun 9, 6:26 pm, Bruce Kroeze <[email protected]> wrote: > Actually, I don't think your issue would be that difficult to work around. > We already monkey-patch Site.objects.get_current. We could instead allow > for an explicit setting of the site before any call to _get_site_id in > sensitive situations. Basically, wrapping the operation with a "no need to > bother the DB, here's your site" operation. I'd accept that patch to > threaded-multihost.multihost_patch.py if you wrote it.
I was afraid that might be the case. Passing a site might not be much more feasible, so it would help if I understood the issue a little more - what problem was the transaction isolation trying to solve? > In addition, and more importantly, Bursar doesn't use Livesettings, because > it is inappropriate to be switching around payment options on-the-fly for > most sites, and because it is unnecessary overhead. Satchmo will shortly be > moving to Bursar for payment processing, and this issue will (mostly) go > away. Sounds good. We'll move onto that when we're able to, I hope. Thanks much, -rob -- You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en.
