Hello, sure do not want to pass the ticket 
https://code.djangoproject.com/ticket/25811?

Please note the full comments of the ticket and give your opinion on the 
solution really that change for me would be, I need to bring a project to a 
second level separating several apps on the basis of various data, and 
there are a lot of code that would touch me correct if these changes do not 
apply. Try to keep the solution generating the subquery, 2 separate 
consultations only apply when the models used belong to different databases.


El sábado, 28 de noviembre de 2015, 18:13:06 (UTC-4:30), Tim Graham 
escribió:
>
> I've also been coordinating the next round of fundraising with Adrienne 
> which includes cleaning up the data for our existing donor records and 
> making some improvements to the website for the next campaign.
>
>
> Triaged
>
> -------
>
> https://code.djangoproject.com/ticket/25799 - list_filter filtering by 
> groups doesn't appear until at least two groups exist (fixed)
>
> https://code.djangoproject.com/ticket/25800 - IIS ISAPI request throws 
> AppRegistryNotReady: Apps aren't loaded yet. (invalid)
>
> https://code.djangoproject.com/ticket/25795 - formfield_for_foreignkey() 
> and limit_choices_to() dont work as expected (duplicate)
>
> https://code.djangoproject.com/ticket/25813 - inspectdb generates 
> incorrect field names for unique_together (duplicate)
>
> https://code.djangoproject.com/ticket/25811 - Error querying across 
> foreign keys with models in different databases (invalid)
>
> https://code.djangoproject.com/ticket/25819 - Allow dumping sql without 
> properly setup database connection (wontfix)
>
> https://code.djangoproject.com/ticket/25821 - Add verbose_name to foreign 
> key fields in django.contrib.admin LogEntry (duplicate)
>
> Authored
>
> --------
>
> https://github.com/django/djangoproject.com/pull/552 - Added NOT NULL 
> constraint to Donation.donor.
>
> https://github.com/django/djangoproject.com/pull/553 - Prevented extra 
> Payment creation for recurring donations.
>
> Reviewed/committed
>
> ------------------
>
> https://github.com/django/django/pull/5674 - Fixed #25767 -- Fixed data 
> truncation possibility with Positive(Small)IntegerField on MySQL.
>
> https://github.com/django/django/pull/5562 - Fixed #25274 --- Made 
> inspectdb handle renamed fields in unique_together.
>
> https://github.com/django/django/pull/5632 - Fixed #25734 -- Made 
> GDALBand min and max properties use GDALComputeRasterStatistics.
>
> https://github.com/django/django/pull/5705 - Fixed #25772 -- Corrected 
> len lookup on ArrayField
>
> https://github.com/django/django/pull/5690 - Fixed #25773 -- Deprecated 
> the geos.MultiPolygon.cascaded_union property.
> https://github.com/django/django/pull/5719 - Fixed #25812 -- Restored the 
> ability to use custom formats with the date template filter.
>
> Reviews of core dev work
>
> ------------------------
>
> https://github.com/django/django/pull/5722 - Fixed #25807 -- Added 
> support for LazyObject serialization in migrations.
>
> https://github.com/django/django/pull/5730 - Fixed #25302 (again) -- 
> Ignored scheme when checking for bad referers.
>

-- 
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 http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/fdfd92cc-93fd-492c-91f7-633b206bc0fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to