On Mon, 2006-09-25 at 13:00 +0200, Manuel Saelices wrote:
> I disagree... You can organizate the information of settings.txt in
> other manner, with a essential settings, and non-essential settings (or
> insignificant settings, as you say) and fix the problem.
And then we have endless threads abo
Given these two example models and sample data:
class Venue(models.Model):
title = models.CharField("title")
class Event(models.Model):
title = models.CharField("title")
venue = models.ForeignKey(Venue, null=True, blank=True)
class Admin:
search_fields = ('
Fixed, though not exactly sure how that error was introduced. The file
where the bug was, I haven't touched in a while. Strange and
random...but it is fixed now.
Chris
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
(Chris),
After a recent update of the row-level branch, every single instance
of every model in the Admin is now getting the "Edit Row Level
Permissions" button on the top right, even the models that don't have
"row_level_permissions = True" in their Meta class.
Jay P.
--~--~-~--~~-
New patch added, now you can use slices and __getitem__On 9/14/06, Rafael SDM Sierra <[EMAIL PROTECTED]
> wrote:Hi again, I've finished my work for now, it's working fine. Please,
someone look the patch3.diff and apply the differences into theirs
respectives files
http://code.djangoproject.com/tic
On 9/22/06, world_domination_kites <[EMAIL PROTECTED]> wrote:
> Carlo C8E Miron wrote:
> > Ciao world_domination_kites,
> > On 9/20/06, world_domination_kites <[EMAIL PROTECTED]> wrote:
> > > I recon what's required is a special cursor encapsulates all that CLOB
> > > foolishness such that calling
I disagree... You can organizate the information of settings.txt in
other manner, with a essential settings, and non-essential settings (or
insignificant settings, as you say) and fix the problem.
But, indeed, is better providing to developer two ways of setting his
develop environment (with opti
Hi.
I have the very first working prototype. Now it works over UDP, using
asyncore library. UDP is unreliable under heavy load, so I don't
recommend using it in production. However, my dispatch system abstracts
event dispatching from the transport, so any suitable transport can be
plugged in. It's
This applies for the current Django trunk. Looks like I don't
understand Django code or there is one unthought use case in
manipulators: When you are updating only a partial set of object fields
in save(), save() fails.
Steps to reproduce
1. Create a change manipulator for an object
2. Update on
