Re: How to make a field that can be inserted but not updated?

t; > > > > If I am not mistaken, editable=False is only applicable to the admin- > > forms. Simply create a view that checks to see if the user is a > > superuser and then give them a form to add an email address. > > > peace, > > -r > > > On Aug 10, 7

How to make a field that can be inserted but not updated?

I am working on an application that includes the following in models.py: class UserEmail(models.Model): email = models.EmailField("email address", unique=True, editable=False) user = models.ForeignKey(UserRegistration) # an email address can only be associated with

Re: Execute a script in manage.py shell

"Maciej Blizinski" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] >On Tue, 2006-07-18 at 22:52 +0200, Maciej Blizinski wrote: >> I already checked the documentation for manage.py, but it doesn't >> mention anything about executing a script. > >Magus- from #django @ Freenode provided

Re: Django and daemon?

"spacedman" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Wouldn't it be better to setup 'procmail' to process incoming emails as > they arrive. Then your procmail script could update the database. Ahh, thanks, it always helps to take the blinders off. The only downside is

Django and daemon?

I'm kind of a newbie at this (web applications, that is, not Python programming), so I'd appreciate any advice others can offer. I'm developing a Django app (post-M-R) that will communicate by email with some remote hosts (which are running archaic software that can't easily be updated to use

Re: No Model Inheritance in Magic-Removal?

"James Bennett" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > On 5/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Now that I knew what I was looking for, I found a note in this page: > > http://code.djangoproject.com/wiki/WikiStart : "[...] so if you need > > model

send_email problem

I see that django.core.email was recently patched to use the DEFAULT_CHARSET setting to encode all outgoing email. This is a problem -- for my application, I want UTF-8 as my default charset for HttpResponses, but I need to be able to send mail in plain ASCII to communicate with a remote host.

Re: One-to-one not to be used?

"James Bennett" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > On 5/12/06, Andrew Badstubner <[EMAIL PROTECTED]> wrote: > > I need to use this, and would love some more information. > From what I understand, one-to-one relationships will be obsoleted by > proper subclassing of