>
> It sounds like you are maybe proposing to decide whether to pre-initialize
> logging with the built-in default config or not based on whether the user's
> LOGGING setting has disable_existing_loggers set to True or False?
>
Yes, I was thinking on my feet and this was one idea I came up with
Hi Ivan,
> On Sep 8, 2016, at 9:00 PM, Ivan Sagalaev wrote:
>
> Actually… I'm failing to imagine a scenario where such a change would lead to
> any bad things:
You may be right, but it's hard to evaluate that without knowing precisely what
change you are envisioning. Can you be more specific
Actually… I'm failing to imagine a scenario where such a change would lead
to any bad things:
- If `disable_existing_loggers` is True, the incompatibility would manifest
itself in Django loggers not being silenced, provided the user has defined
a root logger. Which is probably the intended beha
Maybe the fields from django-mysql help?
http://django-mysql.readthedocs.io/en/latest/model_fields/resizable_text_binary_fields.html
On Thursday, September 8, 2016 at 10:56:15 AM UTC-4, Chris Foresman wrote:
>
> I had a need to store an encrypted bytestring, and CharField doesn't work.
> But Bina
I had a need to store an encrypted bytestring, and CharField doesn't work.
But BinaryField uses LONGBLOB by default (at least on MySQL). Doesn't it
make more sense to have a BinaryField equivalent of CharField, and use
LONGBLOB for something analogous to TextField? As far as I can tell, the
MyS
