Re: Problem with history view in admin page

On Tue, Nov 24, 2009 at 1:07 PM, Mario Briggs wrote: >>> > What is stored in this field is a string-serialized representation of > the > primary key value. > << > > I agree that INTEGER is not the right choice, but then so too is CLOB. > How long is this string-serialized

Re: Problem with history view in admin page

>> What is stored in this field is a string-serialized representation of the primary key value. << I agree that INTEGER is not the right choice, but then so too is CLOB. How long is this string-serialized representation going to be? greater than 4000 characters ? Varchar(X) where X is > 4000 or

Re: Design decision on FileField removing abandoned files?

I'm with you, if not on 100% of what you said, at least 95% of it :) > That said, if throwing directory deleting out > is the thing that's required to get the patch in, I won't object ;) I just foresee that if there is heavy hesitation on even deleting files, deleting directories might be too

Re: Design decision on FileField removing abandoned files?

> It has a kind of goofy option for deleting > empty directories when removing a file leaves said directory empty. Hey, it's not goofy. It's handy ;) I also took _great_ care when writing the code for directory deletion and it's happily deleting directories on our production server since a year

Re: Scaffolding

Hi, I'm working a lot on Model Driven Software Development in the SIDE-Labs project and your approach definitely has a lot of interests for me. We currently chose to work on Alfresco as a framework but we are looking after technological alternatives. Have you been a little further in your

Feedback on ticket 7777

Hi, Can I please get some feedback on this ticket? I am hoping that we can get this in soon. http://code.djangoproject.com/ticket/ Thanks, Farhan -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: Public method for getting model field names in order of definition

> Thanks for the example, but that's not a ModelForm. > > Richard Another try, view.py: from django.forms.models import model_to_dict def view(request): data = Foo.objects.all()[0] print data.start form = Example(data=model_to_dict(data)) return render_to_response('t.html',

Re: Public method for getting model field names in order of definition

On Mon, 2009-11-23 at 04:56 -0800, Anssi Kaariainen wrote: > Here is a working example. > data = {'field1': 'Foo', 'field2': 10} > form = Example(data=data) Thanks for the example, but that's not a ModelForm. Richard -- You received this message because you are subscribed to the Google

Re: Design decision on FileField removing abandoned files?

After some more searching of the current 1.2 tickets, #7048 [1] seems like it does the job. It has a kind of goofy option for deleting empty directories when removing a file leaves said directory empty. If this were merged together with the existing models.FileField class, it would perfectly fix

How hard would it be to make bits of Django compatible with async servers?

I've been getting very excited about Node.js recently: http://simonwillison.net/2009/Nov/23/node/ It's basically Twisted / Tornado but in JavaScript, and with the huge advantage that, because it's brand new, it doesn't have any legacy blocking APIs. Database access looks like this:

Re: Problem with history view in admin page

Note Oracle had the same problem: http://code.djangoproject.com/ticket/5087 I can't actually read Oracle but I think the fix involves adding a cast that extracts the first 4000 chars of data from the field for comparison. They override the field_cast_sql method in the Oracle DatabaseOperations

Re: Problem with history view in admin page

On Mon, Nov 23, 2009 at 9:12 PM, Rahul wrote: > Hi All, > > There is a problem reported for history view in admin page. > For history view there is a sql query generated, which trying to do > exact look-up on OBJECT_ID column (LogEntry model, DJANGO_ADMIN_LOG >

Problem with history view in admin page

Hi All, There is a problem reported for history view in admin page. For history view there is a sql query generated, which trying to do exact look-up on OBJECT_ID column (LogEntry model, DJANGO_ADMIN_LOG table). "TextField" is responsible for handling large text and in DB2 "TextField" is mapped

Re: Public method for getting model field names in order of definition

Here is a working example. I am using svn version of Django, but IIRC this works also in 1.0. views.py: from django.shortcuts import render_to_response from django import forms class Example(forms.Form): field1 = forms.CharField() field2 = forms.IntegerField(label='Labeled') def

#12202 (Hardcoded subject in the reset password mail)

I'm needing a bit of feedback on this ticket[1]. Currently there is no way to specify what the subject line of a password reset email should contain. SmileyChris brought up the question of whether to pass this subject as an argument in the view/form or to use a template. In the patch I have