On Mar 5, 11:08 pm, Ian Kelly wrote:
> On Thu, Mar 5, 2009 at 11:57 AM, Evgeniy Ivanov
> wrote:
>
> > On Mar 5, 6:57 pm, Ian Kelly wrote:
> >> On Thu, Mar 5, 2009 at 8:37 AM, Evgeniy Ivanov
> >> wrote:
>
> >> > Hi!
>
> >> >
On Mar 5, 6:57 pm, Ian Kelly wrote:
> On Thu, Mar 5, 2009 at 8:37 AM, Evgeniy Ivanov wrote:
>
> > Hi!
>
> > I have such code:
> > "name = models.CharField(max_length=32)".
> > Thus "blank=False and null=False" should be applied. But in
Hi!
I have such code:
"name = models.CharField(max_length=32)".
Thus "blank=False and null=False" should be applied. But in DB this
attr is nullable, and since oracle stores empty strings as null
attribute created wrongly (' "NAME " NVARCHAR2 (32) , ').
Should I file a bug?
P.S. I posted to use
12 -0800, Evgeniy Ivanov wrote:
> > On Jan 23, 3:17 am, Malcolm Tredinnick
> > wrote:
> > > Addressing this only in the admin would be short-sighted, however. A for
> > > field that new how to handle reverse relations would be the first step
> > > and then a
On Jan 23, 3:17 am, Malcolm Tredinnick
wrote:
> Addressing this only in the admin would be short-sighted, however. A for
> field that new how to handle reverse relations would be the first step
> and then allowing the admin to use that is the second one.
>
Maybe better approuch is in model's met
On Jan 22, 6:51 pm, Yuri Baburov wrote:
> Hi, and what's wrong with writing a fix for admin to make "inverted"
> m2m relation to show m2m if specified in list_display list? I know
> it's not easy to do for one who is not django creator, but since it's
> open source... ;)
Oh, it could be interest
ere was some discussion in django users:
http://groups.google.com/group/django-users/browse_thread/thread/50bf564e98954a78
On Jan 22, 12:38 am, "Evgeniy Ivanov (powerfox)"
wrote:
> Hi list,
> I had to implement M2M editing in both admin forms (something like
> editing userlist for group
Hi list,
I had to implement M2M editing in both admin forms (something like
editing userlist for group and grouplist for user). I wasn't able to
find any fine solution, but specifying M2M in both models and creating
tables manually (since syncdb tries to create two tables).
I herd in the IRC, that
