Re: History tracking for models

Sorry guys new to this place.:).thanks for da pointers On May 13, 12:49 pm, Justin Lilly wrote: > Take this question to django-users please. Also, check out marty > alchin's pro django foe this snippet. > > -justin > > On May 13, 2009, at 3:36 AM, kailash

Re: Reduce bug triage overhead: DjangoAwesomeBot

On May 12, 2009, at 13:24, J. Clifford Dyer wrote: > I don't see this as a necessary requirement for all patches. What if > the patch has nothing but tests in it, and is improving something that > was sub-optimal or missing altogether in the test code. I'm sure you can find 99

Re: Localization of permissions names

Hi Hendrique, On Wed, May 13, hcarvalhoalves wrote: > Even if this can't or doesn't seem right to be done on the current > state of Django, I would be grateful for some advice on improving the > patch to implement the desired behavior - it's a really needed > feature. you're probably not aware

Re: Localization of permissions names

On May 13, 6:12 pm, Michael Radziej wrote: > Hi Hendrique, > > On Wed, May 13, hcarvalhoalves wrote: > > Even if this can't or doesn't seem right to be done on the current > > state of Django, I would be grateful for some advice on improving the > > patch to implement the desired

Ticket #11107 needs review (was Re: Postgres error with syncdb and flush.)

On Wed, 2009-05-13 at 15:31 -0400, J. Cliff Dyer wrote: > On Wed, 2009-05-13 at 14:40 -0400, J. Cliff Dyer wrote: > > [...] but it occurs to me that if through=MyModel is set on the > > ManyToMany, the sequence on MyModel will already be handled by the loop > > at line 112. I think I can code

Re: Localization of permissions names

On May 13, 5:27 pm, Malcolm Tredinnick wrote: > On Wed, 2009-05-13 at 13:14 -0700, hcarvalhoalves wrote: > > I tried both reopening [1] and filling a new ticket [2], but looks > > like I'm doing it the wrong way as they kept being closed. So here I > > come asking for

Re: Localization of permissions names

On Wed, 2009-05-13 at 13:14 -0700, hcarvalhoalves wrote: > I tried both reopening [1] and filling a new ticket [2], but looks > like I'm doing it the wrong way as they kept being closed. So here I > come asking for help on the list. The reason in both cases was explained in the tickets (and in

Localization of permissions names

I tried both reopening [1] and filling a new ticket [2], but looks like I'm doing it the wrong way as they kept being closed. So here I come asking for help on the list. On syncdb, contrib.auth will create default permissions for each model you have (add, change, delete). But the permission

Re: Postgres error with syncdb and flush.

On Wed, 2009-05-13 at 14:40 -0400, J. Cliff Dyer wrote: > On Wed, 2009-05-13 at 12:49 -0400, J. Cliff Dyer wrote: > > Setup: > > > > Ubuntu 9.04 > > Python 2.6.2 > > Django 1.0.2 > > Postgres 8.3.7 > > postgresql-psycopg2 > > > > I'm having issues using ./manage.py syncdb and ./manage.py flush

Re: Postgres error with syncdb and flush.

On Wed, 2009-05-13 at 12:49 -0400, J. Cliff Dyer wrote: > Setup: > > Ubuntu 9.04 > Python 2.6.2 > Django 1.0.2 > Postgres 8.3.7 > postgresql-psycopg2 > > I'm having issues using ./manage.py syncdb and ./manage.py flush with a > project of mine. I've got an app, venues, which defines a >

Re: model validation

On Wed, May 13, hcarvalhoalves wrote: > Thanks for raising attention on this feature, I wasn't aware of your > "Model Validation" branch and GSOC project. > > One question: I'm afraid of the implications of coupling validation to > models instead of the actual solution (Form/ModelForm). Coupling

Re: model validation

On May 12, 9:28 pm, Honza Král wrote: > Hi, > last week I was busy during EuroDjangoCon, so I am afraid there was > close to no progress on actual work. I did however give a talk on the > topic (see slides at [0]) and got into a few interesting discussions. > As a result of

Postgres error with syncdb and flush.

Setup: Ubuntu 9.04 Python 2.6.2 Django 1.0.2 Postgres 8.3.7 postgresql-psycopg2 I'm having issues using ./manage.py syncdb and ./manage.py flush with a project of mine. I've got an app, venues, which defines a ManyToManyField. After syncdb loads the fixtures, (and only if it tries to load

Re: Decision for ticket #6362 - Remove blank spaces with strip when validating the data

On Wed, May 13, 2009 at 2:36 AM, julianb wrote: > Since the ticket is one year old, that time had come and passed. The ticket's age is irrelevant. *right this minute*, everyone is focused on 1.1, so making a design decision for this ticket is not important right now. Once

Re: History tracking for models

Take this question to django-users please. Also, check out marty alchin's pro django foe this snippet. -justin On May 13, 2009, at 3:36 AM, kailash wrote: > > Hi, >Just want to know is there any way of tracking the history in the > database of a model. > Like..every

Re: History tracking for models

On Wednesday 13 May 2009 08:36:33 kailash wrote: > Hi, > Just want to know is there any way of tracking the history in > the database of a model. > Like..every time i update a row using model.save() , the data that > previously existed gets recorded into any table??? > If there's any such

Re: Django

On Wed, May 13, 2009 at 5:47 PM, ankit wrote: > > how can i customise  list_filter option. > > In my Django model I have a field called status which can have three > choices > 1)activated > 2)rejected > 3)pending > > > > I am using status in list_filter.By default it shows

Re: History tracking for models

On Wed, May 13, 2009 at 3:36 PM, kailash wrote: > > Hi, >    Just want to know is there any way of tracking the history in the > database of a model. > Like..every time i update a row using model.save() , the data that > previously existed gets recorded into any table??? > If

Django

how can i customise list_filter option. In my Django model I have a field called status which can have three choices 1)activated 2)rejected 3)pending I am using status in list_filter.By default it shows me the 'ALL' but i want to set default to pending.

History tracking for models

Hi, Just want to know is there any way of tracking the history in the database of a model. Like..every time i update a row using model.save() , the data that previously existed gets recorded into any table??? If there's any such functionality please let me know..because the module i've

Re: Decision for ticket #6362 - Remove blank spaces with strip when validating the data

On May 13, 2:56 am, Russell Keith-Magee wrote: > We need to wait until we're not trying to get v1.1 out the door. Since the ticket is one year old, that time had come and passed. --~--~-~--~~~---~--~~ You received this message because you