I just checked it out of the repository earlier this week. I'll try
updating and see if that makes a difference.
Todd
On Apr 3, 2006, at 2:29 AM, Bryan Chow wrote:
>
> verbose_name is not required. Are you using the latest revision of
> m-r?
>
>
> >
--~--~-~--~~~--
verbose_name is not required. Are you using the latest revision of m-r?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To uns
Yes, I did run syncdb. I ran it again, just to be sure.
Adding the verbose_name in Meta solves the problem, but commenting it
out brings back "None". Is setting the verbose_name required or is
this just an oversight somewhere?
Todd
P.S. Thanks for being patient. I feel a little between worl
Did you run manage.py syncdb to create the database tables required for
the adminstration interface?
Also, you can specify verbose_name in the Meta class in your model.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Group
That did the trick. (Of course, I had to look up the 'pass' command.
It's fun being a language newbie again. )
But now my three models show up in the Admin interface as 'None'. All
three of them. Which makes it hard to figure out what you're going to
be editing when you pick one. The module
On 4/2/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> I've tried replacing
>
> class META:
> admin = meta.Admin()
>
> with
>
> class Admin:
You need to have
class Admin:
pass
You'll get errors if you don't include the "pass" line if there's
nothing else in the class. That should be e
Tutorial 2 hasn't been updated for magic-removal, yet.
I've tried replacing
class META:
admin = meta.Admin()
with
class Admin:
since that seems to be the message of the magic-removal docs, but I
get an error because there's nothing in the inner class. How do you
set something to u
On 4/2/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> oh, in MR - havent had the nerve to try MR yet
I've stopped using trunk for anything other than answering questions
on the list or in IRC... magic-removal's been stable enough for my
needs for quite some time :)
--
"May the forces of evil
On Sunday 02 Apr 2006 1:17 pm, James Bennett wrote:
> On 4/2/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> > django has transactions? i didnt see any anouncement.
>
> http://code.djangoproject.com/changeset/2457
oh, in MR - havent had the nerve to try MR yet
--
regards
kg
http://www.livej
I solved this another way, today. I move the file to it's new filename
in the save method of the model. It's not fully tested but seems to
work. In my case I use a slug field to create nice filenames.
def save(self):
if self.image:
import shutil
from os import
So, I've been working in m-r for just a couple of days now, and of
course, one of the first things I needed to do was to create a custom
model field -- in this case, ImageField, to get better control over
the filenames that are generated.
I'd like to base the filename on the id field of the model
The order_with_respect_to field seems to be described variously as
"little used" or "neglected"
I've been looking at order_with_respect_to in magic-removal, and it
looks like the code that would enable it (in
django.db.models.Options.get_ordered_objects) has been commented out,
with a "TODO" atta
I finally found my problem:
I tried to get the children of an object by myobject.child_set.all()
(because I set related_name to 'child'), but it should be
myobject.item_set.all() (in your case myobject.person_set.all()).
Thanks for your help!
Rudolph
--~--~-~--~~~-
Hmm, I've had Zope instances that grow to 2 gigs of memory (but are
mainly around the 200-300 Meg region).
Most of our Apache instances have been about 2-8 Megs (php and gd
installed), but I've not done work with mod_python yet, so I have no
numbers there.
Thanks for the info.
Tone.
--~--~
Here's something I'm using in an application - it uses the 'Textile'
engine so that the person entering the markup doesn't have to worry
about HTML. Works well!
It's in a model, and this is all MR by the way;
class Person(models.Model):
...
expectations = models.TextField('Expectations body'
Same here Jacob - can you shed some light on this please? - ;)
(ie __exclude doesn't work)
Cheers,
Tone
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to dj
Yes, it's definitely MR - revision 2530 - I just 'svn up' to 2605 and
the admin interface still works the same. I've just realised that's not
what your problem is, although there are plenty of posts where the word
'parent' is mentioned...
Here's the relevant model definitions for a 'Person'. Work
P.S. I just switched to MySQL as a database backend, switched off the
PostgreSQL instance, and the performance is roughly the same. SO maybe
it ISN'T a Postgres DB problem after all.
Daniel
--~--~-~--~~~---~--~~
You received this message because you are subsc
Thanks! It solved my problem.
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send em
Hi,
For me that didn't solved the problem. Did you try it on Magic Removal?
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegro
Hi,
I noticed the cleaner syntax (really nice!), but I wonder how this
applies to "limit_choices_to".
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email
Hey folks --
Magic-removal replaced the "__ne" and friends with the much-clearer
"exclude()" lookup filter::
People.objects.exclude(firstname="Jacob")
Is the same as trunk's::
people.get_list(name__ne="Jacob")
Jacob
--~--~-~--~~~---~--~~
You
Try replacing 'Item' with 'self' - that works for me.
Cheers,
Tone
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubsc
Hi
I tried this in Magic Removal:
class Item(models.Model):
name = models.CharField('Name', maxlength = 50,)
parent = models.ForeignKey('Item', blank = True, null = True,
related_name = 'child',)
When trying to get the childs of an object by issueing
item.child_set.all(), it raises an e
Hi.
I'm having performance problems with Django under mod_python on my beta
server. I've installed my application on a shared (virtual) server,
running Suse Linux 9.3, with apache2, mod_python and PostgreSQL. The
server is supposed to offer 384MB RAM and is a shared dual-core Itanium
2.6GHz machi
I tried __ne and (somewhat naively) __exclude and neither works.
The Wiki documentation at
http://code.djangoproject.com/wiki/RemovingTheMagic#Changedtemplatenamesingenericviews
says that 'ne is no longer a valid lookup type'
I had a look around and in the MR version of the file
db/backends/mysq
Hi,
I couldn't find it on the mailinglists or on
http://code.djangoproject.com/wiki/RemovingTheMagic:
What is the replacement for the _manipulator_validate_...() methods in
Magic Removal? I would like to do some validation and the exceptions
should be displayed in the admin interface (Validation
Feel free to add it!
--Ned.
akaihola wrote:
> Ned, I think this is definitely Django Cookbook stuff. It would perhaps
> fit in http://code.djangoproject.com/wiki/CookBookDataModels
>
> I can add it for you if you're busy and allow me to... :)
>
>
> >
>
>
> .
>
>
--
Ned Batchelder, http://ne
Hi,
I'm migrating my project to Magic Removal. I couldn't find how to do
the equivalent of the limit_choices_to = {'name__ne' : 'John'} in Magic
Removal.
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Dj
Ned, I think this is definitely Django Cookbook stuff. It would perhaps
fit in http://code.djangoproject.com/wiki/CookBookDataModels
I can add it for you if you're busy and allow me to... :)
--~--~-~--~~~---~--~~
You received this message because you are subscrib
Out of curiosity, I took a look at magic-removal source to see what
changes would be needed for this. I think that in the case of integer
fields it's sufficient to add whitespace into the validation regexp in
core/validators.py:
integer_re = re.compile(r'^\s*-?\d+\s*$')
This should work because P
31 matches
Mail list logo
