./manage.py loaddata calls .save() on all models... should it?

If we'll look into core/management/commands/loaddata we'll see the line "obj.save(using=using)" which saves the data. *however* consider the case when application has some custom database- altering logic in .save method. The common thing that comes to mind is timestamp, or something similar. What

Re: ./manage.py loaddata calls .save() on all models... should it?

Oh okay, apparently there is a ticket from 4 years ago http://code.djangoproject.com/ticket/4459 On Mar 30, 5:21 pm, George Karpenkov wrote: > If we'll look into core/management/commands/loaddata we'll see the > line > "obj.save(using=using)" which saves the data. > >

Re: ./manage.py loaddata calls .save() on all models... should it?

On Wed, Mar 30, 2011 at 2:21 PM, George Karpenkov wrote: > If we'll look into core/management/commands/loaddata we'll see the > line > "obj.save(using=using)" which saves the data. ... and if you dig a little deeper, you'll find that "obj" in that context is a

Re: Proposal: switch to HTML5 for bundled templates

On 30 March 2011 06:55, Matt Harasymczuk wrote: > > Most of users has JS enabled browsers, if so, modernizr works. > Otherwise jQuery will not work either. Most is not all. Even now the admin will work without jQuery, but it won't work without modernizr if you put HTML5 tags

Re: [GSoC Proposal] Customizable Serialization

On Fri, Mar 25, 2011 at 6:03 PM, Vivek Narayanan wrote: >> I think I see where you're going here. However, I'm not sure it >> captures the entire problem. >> >> Part of the problem with the existing serializers is that they don't >> account for the fact that there's actually

Re: [GSoC Proposal] Customizable Serialization

On Wed, Mar 30, 2011 at 4:08 PM, Russell Keith-Magee wrote: > On Fri, Mar 25, 2011 at 6:03 PM, Vivek Narayanan wrote: >>> When you start dealing with foreign keys and m2m, you have an >>> additional set of assumptions -- >>> >>>  * How far should I

Re: ./manage.py loaddata calls .save() on all models... should it?

Oh thanks Russel! Turns out django-tagging was creating those objects via the post-save signal hook. http://code.djangoproject.com/ticket/8399 <- here is the ticket which proposes an option to disable the signal handling during the loaddata operation. Malcolm says that some people might want to

Re: ./manage.py loaddata calls .save() on all models... should it?

On Wed, Mar 30, 2011 at 4:55 PM, George Karpenkov wrote: > Oh thanks Russel! > > Turns out django-tagging was creating those objects via the post-save > signal hook. > > http://code.djangoproject.com/ticket/8399 <- here is the ticket which > proposes an option to disable

Uncaught exception handler

hi, i make a little change to django 1.2.5 according to my needs and i want to know your notes about it. by this patch you can specify a uncaught exception handler in you settings file just like: EXCEPTION_HANDLER = somefunciton and "somefunction" function will be called every time you got an

Re: Uncaught exception handler

Why can't you just create middleware and use process_exception or write python logging handler ? Kristaps Kūlis On Wed, Mar 30, 2011 at 1:48 PM, Sameer Rahmani wrote: > hi, > i make a little change to django 1.2.5 according to my needs and i want > to know your notes

[GSoC] Django Template Compilation rev.2

Django Template Compilation rev.2 = About Me I'm student of last year of Technical University of Lodz, Poland on faculty of electronic engineering and computer science, while now in parallel I'm doing my second diplom of electronic engineering on Polytech

Re: Single Table Inheritance

Hi Jordan, On Tue, Mar 29, 2011 at 08:40:28AM -0700, Jordan MacDonald wrote: > I'm sure this subject has been beaten to death, but I haven't found an > answer to a simple scenario and I'm wondering why this hasn't been > addressed before. > > I have three models, structured like so: > >

Re: Single Table Inheritance

If you need to be able to filter and search across models, you could try haystack. http://docs.haystacksearch.org/dev/searchqueryset_api.html#filter I've setup a site with a real base class, done queries on that and then returned the child classes. It worked, but it felt pretty hacky all the way

Re: HBase backend support

Hi, I plan to implement HBase backend support for Django as part of GSoC 2011. Before I flesh out the idea in detail, I would like to know if this is useful enough to Django, whether there are alternatives to using HBase in the first place. -- You received this message because you are

Re: HBase backend support

On 30/03/11 12:58, Rohit wrote: > Hi, > I plan to implement HBase backend support for Django as part of > GSoC 2011. Before I flesh out the idea in detail, I would like to know > if this is useful enough to Django, whether there are alternatives to > using HBase in the first place. Hi Rohit,

Re: HBase backend support

On Wed, Mar 30, 2011 at 7:58 PM, Rohit wrote: > Hi, >     I plan to implement HBase backend support for Django as part of > GSoC 2011. Before I flesh out the idea in detail, I would like to know > if this is useful enough to Django, whether there are alternatives to > using

Instructions for code changing to Django 1.3

I have a project running in Django 1.2.5 and I want to update it (the code) to Django 1.3. I've seen the release notes, but there is no direct instructions to *what I have to change in the code*. It would be very useful to me, to all the community (I know that a lot of people may be in the exact

Re: Instructions for code changing to Django 1.3

What's wrong with the release notes[1]? They contain a list of backwards incompatible changes [2], which is the only this you'd need to change. [1]: http://docs.djangoproject.com/en/dev/releases/1.3/ [2]: http://docs.djangoproject.com/en/dev/releases/1.3/#backwards-incompatible-changes-in-1-3

Re: Proposal: switch to HTML5 for bundled templates

2011/3/30 Łukasz Rekucki > On 30 March 2011 06:55, Matt Harasymczuk wrote: > > > > Most of users has JS enabled browsers, if so, modernizr works. > > Otherwise jQuery will not work either. > > Most is not all. Even now the admin will work without jQuery,

Re: HBase backend support

On Wed, Mar 30, 2011 at 6:40 PM, Russell Keith-Magee < russ...@keith-magee.com> wrote: > On Wed, Mar 30, 2011 at 7:58 PM, Rohit wrote: > > Hi, > > I plan to implement HBase backend support for Django as part of > > GSoC 2011. Before I flesh out the idea in detail, I

Re: New messages API: regressions ?

On Tue, Mar 29, 2011 at 11:08 AM, is_null wrote: > Greetings hackers, > > Django offered a feature to add messages to offline users, or to add > messages to users in slots (if that's the pythonic name for "functions > connected to signals"). It is still possible before 1.4,

Re: Django Template Compilation rev.2

On Mar 30, 6:18 am, xtrqt wrote: >     def templ(context, divisibleby=divisibleby): >         my_list = context.get("my_list") >         _loop_len = len(my_list) >         result = [] >         for forloop, i in enumerate(my_list): >             forloop = { >              

GSoc : Templates Compilation

I'm interested in participating in your mentors program in Google Summer Code. Looking at the template implementation I've seen that I can make some solutions for implementation compiling in bytecode templates. Just adding function «compile» to every Node-derived class and modifying/ adding new

GSOC : Django auth

I'm interested in participating in your mentors program in Google Summer Code. Clearly looking on the current situation with authentication, authorisation, customization of users, I could say that there is no simple solution for achieving all possible modifications of user auth subsystem. I would

Re: GSoc : Templates Compilation

How exactly do you want to solve dynamic inheritance? It seems that some people are still interested in dynamic inheritance, by using {% extends variable %}. (Which is still dirty in my opinion, but anyway.) Block information has to be kept somehow. Maybe one small improvement. Isn't the

Re: GSOC : Django auth

On Thu, Mar 31, 2011 at 1:30 AM, Andrey Zubko wrote: > I'm interested in participating  in your mentors program in Google > Summer Code. > Clearly looking on the current situation with authentication, > authorisation, customization of users, I could say that there is no >

Re: GSOC : Django auth

On 03/30/2011 07:43 PM, Russell Keith-Magee wrote: > ... and this is the exact model that has been proposed, and rejected > in #3011 (albeit with a more complex dance around default values). It I just re-read #3011, and it is far from clear from reading through the ticket that that approach was

ibm_db_django-1.0.2 IBM Dataservers backend support for Django 1.3 Released

IBM_DB_DJANGO-1.0.2 --- IBM_DB_DJANGO adaptor enables access to IBM databases from Django applications http://www.djangoproject.com/. The adaptor is developed and maintained by IBM. What's New? - Added support for Django-1.3 - Backward