Re: Read only fields once created

2006-12-07 Thread Ross Burton
MerMer wrote: > You can add "editable=False" to you database model. This prevents it > from showing up in Admin, though of course it can still be edited > directly in the DB. This stops it being set in the admin when creating a new object, which isn't what I want. I think I'll have to hack the

Re: Read only fields once created

2006-12-06 Thread MerMer
You can add "editable=False" to you database model. This prevents it from showing up in Admin, though of course it can still be edited directly in the DB. MerMer Ross Burton wrote: > Hi, > > Is it possible to have fields in the model that can be set at object > creation, but are immutable a

Re: Read only fields once created

2006-12-06 Thread Sarcastic Zombie
On Dec 6, 2:48 pm, "Sarcastic Zombie" <[EMAIL PROTECTED]> wrote: > On Dec 5, 3:24 am, "Ross Burton" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > Is it possible to have fields in the model that can be set at object > > creation, but are immutable after that? I have an "original estimate" > > field

Re: Read only fields once created

2006-12-06 Thread Sarcastic Zombie
On Dec 5, 3:24 am, "Ross Burton" <[EMAIL PROTECTED]> wrote: > Hi, > > Is it possible to have fields in the model that can be set at object > creation, but are immutable after that? I have an "original estimate" > field that should only be set when creating the object, and never > edited after tha

Read only fields once created

2006-12-05 Thread Ross Burton
Hi, Is it possible to have fields in the model that can be set at object creation, but are immutable after that? I have an "original estimate" field that should only be set when creating the object, and never edited after that. Thanks, Ross --~--~-~--~~~---~--~