I guess the aim of documaentation is to be helpful and assist the end user. While it makes no sense to document mysql within Django, wouldn't it make sense to document specific interactions between Django and it's supported back-end DB's that are likely to catch people out? - maybe just as annotations to the main text?
I personally find I appreciate such things hugely when reading through documentation etc.. - It does nothing but good for me and my perception of the materials at hand. ? On 6 March 2010 12:50, Masklinn <maskl...@masklinn.net> wrote: > On 6 Mar 2010, at 05:43 , Ilya Braude wrote: > > > > Karen Tracey wrote: > >> I'm guessing you are using MySQL That's just how it behaves, by default. > See: > >> > >> > http://dev.mysql.com/doc/refman/5.1/en/server-session-variables.html#sysvar_sql_auto_is_null > > > > Wow, thanks. I now see that this has been brought up a few times before. > This MySQL behavior should really be documented somewhere in Django. > That doesn't make any sense. It's a MySQL behavior, not a django one, > should Django document each and every misbehavior of each and every database > it supports? > > > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
