Re: Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

About idea of use settings.py to set a default site, -1 About ask to user what is yours default site, +1 This thing only runs at syncdb, so I really don't think that a entry in settings.py is needed. 2010/5/18 Oldřich Jedlička > Hi, > > 2010/3/19 dalore

Re: Django Transaction Integrity

Ian, thanks for the feedback, but what your concern is not related to this proposal. What you're talking about is issuing a BEGIN while already in a database transaction, which is normally an error, with no standard meaning or definition in SQL's transaction model. It's completely up to the

Re: Patch for #6870: sending pre_delete before caching of related models

On Tue, May 18, 2010 at 4:41 AM, Carl Gieringer wrote: > Hi Djangonauts, > > I'd like to call attention to a patch[0] I submitted last week for > #6870[1].  From one perspective, this ticket is a version of the "My > models with foreign keys are deleted when their

Re: Some bugs in manage multidb

On Tue, May 18, 2010 at 5:08 PM, Alberto Paro wrote: > I'm developing a big application that does some complex mixing of database: > SQL and notSQL one. > I'm using the multidb to manage all the stuff in a django manner, using > routing to route items in MongoDB and

Re: Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

Hi, 2010/3/19 dalore > Because of this thread I decided to release a little app we have been > using internally. It's a straightforward way to modify the default > site object. > > More details: http://oppian.com/labs/django-defaultsite/ > > Any comments/suggestions welcome.

Re: 1.1.2 admin form regression

On May 18, 5:41 pm, Karen Tracey wrote: > On Tue, May 18, 2010 at 12:45 AM, SmileyChris wrote: > > Can't investigate too much more until tomorrow, but it's a pretty big > > regression so I thought I'd bring it up here for discussion as well as > >

Some bugs in manage multidb

I'm developing a big application that does some complex mixing of database: SQL and notSQL one. I'm using the multidb to manage all the stuff in a django manner, using routing to route items in MongoDB and Postgresql. Some bugs that I've discovered: 1) django is unable to manage different

Re: Django Transaction Integrity

> Yes: we're talking about Django's transaction management layer (that is, the > code in django.db.transaction), which controls how Python-level transaction > blocks map to SQL transactions. > > The original email and writeup has a full explanation. :) > Yes. What I was getting at is that

Re: Django Transaction Integrity

2010/5/18 Ian Lewis : > Am I missing something? Are we talking about doing some kind of > transaction management at the application level? Yes: we're talking about Django's transaction management layer (that is, the code in django.db.transaction), which controls how