On 4/19/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> On 4/19/06, argus <[EMAIL PROTECTED]> wrote:
> >
> > Is there any reason that there's not a way to specify/override the size
> > of the form field that gets used in templates (separately from what
> > gets used in the admin interface)? I
On 4/19/06, argus <[EMAIL PROTECTED]> wrote:
>
> Is there any reason that there's not a way to specify/override the size
> of the form field that gets used in templates (separately from what
> gets used in the admin interface)? I can't think of one, and it's been
> something of a thorn in my
Is there any reason that there's not a way to specify/override the size
of the form field that gets used in templates (separately from what
gets used in the admin interface)? I can't think of one, and it's been
something of a thorn in my side recently, so I figured I'd ask :) I'm
reluctant to
I am trying to do something pretty basic here -- I even worked out how
to do it earlier but now I have forgotten so I need a nudge in the
right direction.
I have a model set up where an item has an owner, simple foreign key
relationship. I have checked everything I modeled works nicely in the
On 4/19/06, PythonistL <[EMAIL PROTECTED]> wrote:
> As to CHANGE manipulator, I do not know how to fill in (prepopulate)the
> form with the data, being changed, from the database. Any idea?
If you want to pre-populate the form data, you just need to be able to
set new_data to hold the data from
Russell Keith-Magee wrote:
> If you have a use case in magic-removal where "self" is the only
> allowed string, then you have probably found a bug. Is this the case,
[Jumpin into youses conversation with just such a bug]
class Foo(models.Model):
myfield = models.OneToOneField('SomeModel',
Luke Plant wrote:
> As I understand it, Django should be able to do this query no problem.
> I think there may be a mistake in what you posted though - IIRC, I
> would have expected the method name to be 'get_articles_list' not
> 'get_article_list', since you defined it as 'articles =
>
Russell Keith-Magee schrieb:
> On 4/19/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
>>No, not really. The only string is "self" ;-)
>
>
> To clarify my point:
>
> 0.91 - "self" is the only string
> magic-removal: "self" and "model-name" are allowed
>
> If you have a use case in
On 4/19/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> Russell Keith-Magee schrieb:
> > Unfortunately, this isn't possible in 0.91/trunk. However, in the
> > magic-removal stream, you can forward reference a model using the string
> > version of the model name.
>
> No, not really. The only
Ian,
Thanks for your reply.
I implemented custom manipulator for ADDing but do not know how to do
that for CHANGING.
class ProductManipulator(formfields.Manipulator):# ADD manipulator
def __init__(self):
.
Several days? several weeks? several months? or several years?
If too far,I will use 0.91 version.
--
http://www.flyaflya.com powered by pygame+python
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users"
> Am I approaching the problem in the wrong way? how can i access custom
> manager functions for Bar, via baz? It throws an error complaining of
> RelatedManager...how can I write my own RelatedManager?
What error does it throw?
Luke
--~--~-~--~~~---~--~~
You
Russell Keith-Magee schrieb:
> Unfortunately, this isn't possible in 0.91/trunk. However, in the
> magic-removal stream, you can forward reference a model using the string
> version of the model name.
No, not really. The only string is "self" ;-)
I tried it a few weeks ago. But if you can
I vaguely remember an advice to use __isnull in a similar situation.
Maybe one of these discussions turns up something useful:
http://simon.bofh.ms/logger/django/search/?q=isnull
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
14 matches
Mail list logo