Comments on: ModelChoiceFields as CharFields in Django

By: OceanTara Code Blog » Blog Archive » use InlineModelChoiceField for hidden foreign key relationships in django

Sat, 21 Feb 2009 22:05:23 +0000

[...] http://www.davidcramer.net/code/109/modelchoicefields-as-charfields-in-django.html [...]

By: Elliott

Elliott — Wed, 26 Mar 2008 21:38:34 +0000

That would be AWESOME; thanks for being such a big contributor to OS.

By: David

David — Wed, 26 Mar 2008 19:21:29 +0000

I’m using a mootools component, and just a custom view to spit it out. I’m planning out distributing my newfroms utilities here in the near future, which will include some sort of ajax controls.

By: Elliott

Elliott — Wed, 26 Mar 2008 19:13:39 +0000

Thanks for this. Its almost exactly what I needed.
Any chance that you could enlighten us on the auto complete stack that you are using?

By: Michael

Michael — Wed, 26 Mar 2008 10:55:30 +0000

get_internal_type() is for model fields only (unrelated to newforms);

I’m actually in need of something similar right now, but I’m not comfortable with using a name string for defining the selection – primarily since I can’t guarantee uniqueness. Instead I’m using a hidden field to pass the id, which the JQuery autocomplete widget from bassistance.de supports nicely using the .result() hook (not sure what you are using of course).

By: David

David — Wed, 26 Mar 2008 10:18:08 +0000

I don’t know much about newforms internals beyond what I’ve hacked out of it, so you may need get_internal_type (but this works).

As for the .filter().get() I think I had it doing .filter()[0:1] at first, so that’s just a slip on my part.

By: Fidel Ramos

Fidel Ramos — Wed, 26 Mar 2008 10:14:11 +0000

Very interesting, the flexibility of Django’s newforms doesn’t cease to amaze me.

Is this code intended for trunk? Wouldn’t you need to define get_internal_type()?

Also, is there a good reason to use filter(name=value).get() instead of get(name=value)?