+1
I am assuming the deprecation is done according to the process that was
discussed in the thread "An easier path to upgrade from one LTS release to
another".
On Sunday, July 12, 2015 at 4:53:23 PM UTC+2, James Bennett wrote:
>
> There's not much to this, really, except what's in the subject
That's also a viable alternative, although it also mention unlogged tables,
which are not supported by django.
We could list the quick hint with config sample, a link to pg non durable
options page and a warning that UNLOGGED tables are not supported yet. What
do you think about this?
BTW has
Thanks for brining this to my attention, Tim! I just commented on the
issue: https://code.djangoproject.com/ticket/25068#comment:12
/Markus
On Thu, Jul 09, 2015 at 01:13:11PM -0700, Tim Graham wrote:
To someone with experience with metaclasses,
A high-level overview of this ticket/pull
Consistently bloody amazing.
Thanks for doing such a great job.
--
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
I see a thirty second increase in the test suite (from 7.5 minutes to 8
minutes) on my local machine with:
sql_create_table = "CREATE UNLOGGED TABLE %(table)s (%(definition)s)"
On Tuesday, July 14, 2015 at 4:20:45 AM UTC-4, Federico Capoano wrote:
>
> That's also a viable alternative, although
