Re: The related_name of ForeignKey cannot be Unicode name after Django 1.8

2015-06-22 Thread Cheng-Hung Hsueh
I have posted in https://code.djangoproject.com/ticket/25016#ticket .

Tim Graham於 2015年6月23日星期二 UTC+8上午12時30分48秒寫道:
>
> It looks like the check added in ticket #22064 may be too strict (only 
> allowing alphanumeric characters in related_name). Would you like to open a 
> ticket?
>
> On Monday, June 22, 2015 at 11:28:50 AM UTC-4, Cheng-Hung Hsueh wrote:
>>
>> This code can run before django 1.7
>> But "related_name" got an error after django 1.8
>>
>> 使用者表.來源: (fields.E306) The name '使用者' is invalid related_name for field 
>> 使用者表.來源
>>
>>
>> class 來源表(models.Model):
>> 名 = models.CharField(max_length=100)
>>
>> class 使用者表(models.Model):
>> 來源 = models.OneToOneField(來源表, related_name='使用者', primary_key=True, 
>> null=False)
>>
>>
>> Is it a bug? I know adding many checks in Django 1.8
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1b762fd2-3fea-480b-9d60-535adafb4209%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: The related_name of ForeignKey cannot be Unicode name after Django 1.8

2015-06-22 Thread Tim Graham
It looks like the check added in ticket #22064 may be too strict (only 
allowing alphanumeric characters in related_name). Would you like to open a 
ticket?

On Monday, June 22, 2015 at 11:28:50 AM UTC-4, Cheng-Hung Hsueh wrote:
>
> This code can run before django 1.7
> But "related_name" got an error after django 1.8
>
> 使用者表.來源: (fields.E306) The name '使用者' is invalid related_name for field 
> 使用者表.來源
>
>
> class 來源表(models.Model):
> 名 = models.CharField(max_length=100)
>
> class 使用者表(models.Model):
> 來源 = models.OneToOneField(來源表, related_name='使用者', primary_key=True, 
> null=False)
>
>
> Is it a bug? I know adding many checks in Django 1.8
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/279ee276-297d-4b40-afe3-917167ffaf44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


The related_name of ForeignKey cannot be Unicode name after Django 1.8

2015-06-22 Thread Cheng-Hung Hsueh
This code can run before django 1.7
But "related_name" got an error after django 1.8

使用者表.來源: (fields.E306) The name '使用者' is invalid related_name for field 
使用者表.來源


class 來源表(models.Model):
名 = models.CharField(max_length=100)

class 使用者表(models.Model):
來源 = models.OneToOneField(來源表, related_name='使用者', primary_key=True, 
null=False)


Is it a bug? I know adding many checks in Django 1.8

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/453092fc-deca-422b-a405-e32ad3b41b1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.