Re: Improving MSSQL and Azure SQL support on Django

2016-01-26 Thread Cristiano Coelho
I'm interested in the progress of this as well :) Sorry I didn't read through all the posts, mostly the first ones about the idea. I would like to know, have you guys decided on which adapter to use? I have had a project where we needed to connect to SQL Server from a linux machine (actually a

Re: deadlock risk from using cache a load time

2016-01-26 Thread Tim Graham
Oops again... sorry for poor memory about the error message. Regarding the original issue -- in Claude's use case, he says that calling django.setup() before unpickling is not doable, as an external tool is doing the unpickling of model data. Should we say that unpickling model data from non-Dj

Re: deadlock risk from using cache a load time

2016-01-26 Thread Aymeric Augustin
On 26 janv. 2016, at 14:40, Tim Graham wrote: > Something like "Models aren't loaded yet. Are you missing django.setup() in a > standalone script?". We’ve had this discussion before, cf. 8121860be4b9379d107959290e5748bbaf6de1fe ;-) The exception message could point to the “Troubleshooting” s

Re: Module Index

2016-01-26 Thread Doug Epling
Tim -- I guess that was an affirmative answer to my question. So I will give it some thought, read the relevant docs, and do what you say. Thanks, On Tuesday, January 26, 2016 at 6:52:08 AM UTC-5, Tim Graham wrote: > > Feel free to file a ticket and/or submit a patch. > > On Tuesday, January

Re: deadlock risk from using cache a load time

2016-01-26 Thread Tim Graham
Oops, here's the pull request: https://github.com/django/django/pull/6044 WIth the fix reverted and the missing django.setup() call, the exception is "django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet.". I don't think we need a different exception in model_unpickle(), but mayb

Re: deadlock risk from using cache a load time

2016-01-26 Thread Aymeric Augustin
> On 26 janv. 2016, at 09:57, Florian Apolloner wrote: > > Revert yes, but a check like that should stay and maybe raise an error > instead of calling apps.populate. The following line, `apps.get_model(…)`, raises an exception when `not apps.models_ready`. -- Aymeric. -- You received th

Re: Module Index

2016-01-26 Thread Ned Batchelder
On 1/25/16 10:05 PM, Doug Epling wrote: shouldn't this be here: https://docs.djangoproject.com/en/1.9/py-modindex/#t The module index is built from directives like ".. module: django.template.loader" in the various .txt files, like docs/topics/templates.txt. Adding more directives will add

Re: Module Index

2016-01-26 Thread Tim Graham
Feel free to file a ticket and/or submit a patch. On Tuesday, January 26, 2016 at 6:05:55 AM UTC-5, Doug Epling wrote: > > shouldn't this be here: > https://docs.djangoproject.com/en/1.9/py-modindex/#t > -- You received this message because you are subscribed to the Google Groups "Django dev

Module Index

2016-01-26 Thread Doug Epling
shouldn't this be here: https://docs.djangoproject.com/en/1.9/py-modindex/#t -- 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 emai

Re: deadlock risk from using cache a load time

2016-01-26 Thread Florian Apolloner
On Tuesday, January 26, 2016 at 9:52:01 AM UTC+1, Aymeric Augustin wrote: > > However I think there's a bigger problem with this code. apps.populate() > should only be called by django.setup(). I think we should > revert 108b8bf852c76855ed98f5abe55db1da845598e7. > Revert yes, but a check like th

Re: deadlock risk from using cache a load time

2016-01-26 Thread Aymeric Augustin
> On 26 janv. 2016, at 00:43, John Bazik wrote: > > In db/models/base.py, in model_unpickle, I see this: > > if isinstance(model_id, tuple): > if not apps.ready: > apps.populate(settings.INSTALLED_APPS) > model = apps.get_model(*model_id) > > Can that test instea