Re: 1.2 beta?

On Tue, Jan 26, 2010 at 9:05 AM, Russell Keith-Magee wrote: > On Tue, Jan 26, 2010 at 2:55 AM, Jacob Kaplan-Moss wrote: >> Hey folks -- >> >> Are we on track for releasing a 1.2 beta this week? >> >> That'd match our original schedule, but we did miss 1.2 alpha by a >> week or so, so perhaps we s

Re: 1.2 beta?

On Tue, Jan 26, 2010 at 7:09 AM, Luke Plant wrote: > On Monday 25 January 2010 18:55:34 Jacob Kaplan-Moss wrote: >> Hey folks -- >> >> Are we on track for releasing a 1.2 beta this week? >> >> That'd match our original schedule, but we did miss 1.2 alpha by a >> week or so, so perhaps we should pu

Re: 1.2 beta?

On Tue, Jan 26, 2010 at 2:55 AM, Jacob Kaplan-Moss wrote: > Hey folks -- > > Are we on track for releasing a 1.2 beta this week? > > That'd match our original schedule, but we did miss 1.2 alpha by a > week or so, so perhaps we should push back the beta to match? Or is > everyone happy with progre

Re: Translation patch and the I18N mailinglist

On Tue, Jan 26, 2010 at 6:06 AM, TiNo wrote: > Hi, > The reason I posted there was to see if anybody had any objections to the > one-liner patch [2] I suggested for a dutch translation that is wrong at the > moment. It would be really nice to see this checked in for 1.2, as it has > been looking q

Subclassing models.Model to extend base functionalities and attributes

Hi everybody, Is there a way to subclass the 'models.Model' class behavior to extend base functionnalities and attributes to all classes contained in an application model ? It seems that the metaclass mechanism force the Python inheritance notation to a Database model inheritance. Thanks, Thierr

Re: App / Model specific database solution

On Mon, Jan 25, 2010 at 8:21 PM, Yuri Baburov wrote: > Hi Russell, > > regarding that doc page, > > there's a typo, please remove that hanging "admin.site.register": > class PublisherAdmin(MultiDBModelAdmin): >    inlines = [BookInline] > >    admin.site.register Done - thanks for the report, Yur

Re: App / Model specific database solution

Hi Russell, regarding that doc page, there's a typo, please remove that hanging "admin.site.register": class PublisherAdmin(MultiDBModelAdmin): inlines = [BookInline] admin.site.register On Mon, Jan 25, 2010 at 5:53 PM, Russell Keith-Magee wrote: > On Mon, Jan 25, 2010 at 7:31 PM, Bill

Re: App / Model specific database solution

Thanks Russ, I'll checkout the database router feature. Regards, Bill On Jan 25, 2010, at 6:53 AM, Russell Keith-Magee wrote: > As of r12272 (committed about three days ago), the best approach to > this problem is to define a database router that directs queries on a > particular object type

Re: App / Model specific database solution

On Mon, Jan 25, 2010 at 7:31 PM, Bill Hubauer wrote: > > > Hi all, > > Given the new multi-db implementation, I put together a couple of little > "helper" classes to make app specific, or model specific databases really > easy. > > Please consider the following and let me know if you think this

App / Model specific database solution

Hi all, Given the new multi-db implementation, I put together a couple of little "helper" classes to make app specific, or model specific databases really easy. Please consider the following and let me know if you think this is too abusive of the internals of the multi-db implementation. Any

Re: possible bug in count() in many_to_many relations?

Hello, 2010/1/25 x13 : > > > On Jan 24, 9:16 pm, Russell Keith-Magee > wrote: > > Thanks for your answers guys, > >> I'm assuming that you feel the right answer here is to return 0? > > yes, IMHO the count() function have to return an integer value without > any exceptions. I disagree. If you're

Re: Possible bug in messages framework?

I just want to say that everything you guys are talking about is so totally over my head, but I'm stoked you're working it out. Thanks, guys. :) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-dev