2011/3/24 dy :
>
> I want to know if I continue to use it like this what problems will
> happen.If you or someone else have this experience,can you tell me?
Being an unsupported setup, I'd say you are in unexplored territory here
so you will need to find the potential shortcomings by yourself.
On
On 3月24日, 下午3时53分, Russell Keith-Magee
wrote:
> On Thu, Mar 24, 2011 at 3:15 PM, dy wrote:
> > Hi Jacob:
>
> >Yes, you understand right!Thank you for your reply.
>
> > As you said,is this a bug of django1.2.3? Or this feature can be used
> > in django-1.2.3, but at a higher version is disable
On Thu, Mar 24, 2011 at 3:15 PM, dy wrote:
> Hi Jacob:
>
> Yes, you understand right!Thank you for your reply.
>
> As you said,is this a bug of django1.2.3? Or this feature can be used
> in django-1.2.3, but at a higher version is disabled.
>
> Moreover, in the official documentation(on this pa
Hi Jacob:
Yes, you understand right!Thank you for your reply.
As you said,is this a bug of django1.2.3? Or this feature can be used
in django-1.2.3, but at a higher version is disabled.
Moreover, in the official documentation(on this page:http://
docs.djangoproject.com/en/1.3/topics/db/multi
Howdy --
On Tue, Mar 22, 2011 at 5:17 AM, dy wrote:
> # model in app test2,store to test2
> class Test2(models.Model):
> name = models.CharField(max_length=30,verbose_name="test2")
> test1 =
> models.ForeignKey('test1.Test1',verbose_name="FK_test1",blank=True,null=True)
Just to be sure I'm
5 matches
Mail list logo