Re: Django OperationalError

Hello James, will do but I am not at mine lap top atm, gona do it as soon as posible, tank you very much. On Saturday, February 28, 2015, James Schneider wrote: > Generally this happens when you don't apply the initial migration. Have you run 'python manage.py migrate' (assuming Django >= 1.7 sin

Re: Django OperationalError

Generally this happens when you don't apply the initial migration. Have you run 'python manage.py migrate' (assuming Django >= 1.7 since you mentioned making migrations) and if you have, what was the output? If you aren't sure, run it again as it shouldn't hurt anything. Check your database and ma

Django OperationalError

Hello, I have manage to merge mine application to pythonanywhere.com. After I have done all the needed installing, uploading files, collecting static, making migrations to mine django application, I have experienced an OperationError saying: no such table: django_session You can find the rest

Re: Migrations force me to have, forever, any name/reference I use in field validators=, choices=, whatever, valid forever (even if the requirements change).

Hello, another solution may be to patch your models in the migration module or class, like: import myapp.models myapp.models.valid_identifier = something_acceptable() Although it seems a bit ugly, I just tested it, and it works. This way valid_identifier will live during the migration only. Be

Re: Model field with default value and choices is always reported as changed, even if unchanged

Am 26.02.2015 um 19:06 schrieb Carsten Fuchs: The expected output is `False`,[...] Just for future reference, this is continued here: https://code.djangoproject.com/ticket/24428 Best regards, Carsten -- You received this message because you are subscribed to the Google Groups "Django users"

Re: Migrations force me to have, forever, any name/reference I use in field validators=, choices=, whatever, valid forever (even if the requirements change).

Thanks :D Did not think about squashing migrations as solution for this problem! But it does the job. OTOH the fact about historical models has nothing to do with my problem (since it is not related at all with instancing a model, but just about the definition and not getting a NameError). --

Did you try NamedUrlWizardView ? I tried example code but does not work ;-(

File ... ... site-packages\django\views}generic\base.py line 60 "attributes of the class." % <(cld.__nsmr__,key) TypeError: ApplyWizard() received an invalid keyword 'url_name'. as_view only accepts arguments that are already attributes of the class. If somebody got NamedUrlWizardView working, l

Re: djangoproject.com https access problems

The proxy is likely forcing a TLS fallback in a way that Firefox doesn't like. Ensure you are using the latest version of FF, but even then, unless you have control off the proxy, there may not be much you can do except open a support ticket with your IT department. https://bugzilla.mozilla.org/sh

djangoproject.com https access problems

Hi, at home it works, but in my company the proxy refuses the connection to: https://www.djangoproject.com and my firefox gives me an error: ssl_error_inappropriate_fallback_alert Question: since when did you switch the website to https (or didn't I notice it) Other sites seems to work, is th

Re: Research: Translations od documentation

I thought there was a plugin for that? You can also do some research and find some articles on how to implement it. On Thursday, 26 February 2015 05:11:21 UTC-5, Tomáš Ehrlich wrote: > > Hello, > tonight is regular python/ruby meetup in Brno (Czech republic)

Re: Can the new `Prefetch` solve my problem?

On Feb 27, 2015 12:51 AM, "aRkadeFR" wrote: > > Yeah, but from my experience, your example through a new > query. You have to (and please correct me if I'm wrong or > there are other ways) use the self.chair_set.all() in order > to not through a new query when you have prefetched the > chairs. AF

Re: Can the new `Prefetch` solve my problem?

Yeah, but from my experience, your example through a new query. You have to (and please correct me if I'm wrong or there are other ways) use the self.chair_set.all() in order to not through a new query when you have prefetched the chairs. To be simple and answer the problem: my only solution I ha