On Mon, May 15, 2017 at 10:30 AM, Tim Chase <django.us...@tim.thechases.com> wrote:
> On 2017-05-15 08:54, Tim Graham wrote: > > Does anyone know of a use case for using null bytes in > > CharField/TextField? > > Is this not what BinaryField is for? It would seem to me that > attempting to store binary NULL bytes in a CharField/TextField should > result in an error condition. > The null byte is also a valid Unicode code point [0]. I guess I'm a bit surprised that a valid code point can't be stored in a PostgreSQL text column. This does appear to be documented for the char(int) string function [1], although without justification. > The NULL (0) character is not allowed because text data types cannot store such bytes. I'm curious behind PostgreSQL's decision to prohibit this code point. If anyone has additional information to share on their reason, please pass it along. [0] http://www.fileformat.info/info/unicode/char/0000/index.htm [1] https://www.postgresql.org/docs/current/static/functions-string.html Cheers -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CADhq2b6egRaJ8t23HRXwjfqTHjTJx%3DjRPSL8P%3D6MUTyotFsP6w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
