python inspectdb got "The error was: function unnest(smallint[]) does not exist"

I use Amazon Redshift database and Django 2.0.6. My redshift database settings is as below: DATABASES = { 'default': { 'NAME': 'my_db_name', 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'USER': 'my_username', 'PASSWORD': 'my_password',

django simple captcha issue

Hi all, I am using django-simple-captcha, it works fine on my dev environment (windows). But after i deployed to linux server, all other views/pages are working fine. But when i request /captcha/image/{{imagekey}}/ i got server internal error 500. Something I missed to configure? Thanks a lot

django queryset issue

Hi all, Here is my question details http://stackoverflow.com/questions/2915880/django-objects-all-method-... this is driving me crazy, after a save(), i can see the new data in mysal db, but i cannot get new data from queryset. Thanks in advance. -- You received this message because you are

Re: how to activate DJANGO.CORE.CONTEXT_PROCESSORS.REQUEST

ke a charm! Thanks again! On Feb 4, 11:54 am, Karen Tracey <kmtra...@gmail.com> wrote: > On Thu, Feb 4, 2010 at 2:39 PM, weiwei <online.service@gmail.com> wrote: > > Thanks.. > > > Here is my code > > You repeated the code for the template tag and the context

Re: how to activate DJANGO.CORE.CONTEXT_PROCESSORS.REQUEST

processors.auth", "django.core.context_processors.debug", "django.core.context_processors.i18n", "django.core.context_processors.media", ) in settings.py On Feb 4, 11:17 am, Karen Tracey <kmtra...@gmail.com> wrote: > On Thu, Feb 4, 2010 at 1:41 PM, weiwei <online.service

how to activate DJANGO.CORE.CONTEXT_PROCESSORS.REQUEST

"DJANGO.CORE.CONTEXT_PROCESSORS.REQUEST If TEMPLATE_CONTEXT_PROCESSORS contains this processor, every RequestContext will contain a variable request, which is the current HttpRequest. Note that this processor is not enabled by default; you'll have to activate it. " from this page

dump utf8 data from database

Hi all, is there a easy way to dump utf8 data from database? Thanks -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to

django fuzzy string translation not showing up

1)why sometimes i got 'fuzzy' item in django.po language file . Actually i have checked in my project the 'fuzzy' string item is totally unique. #: .\users\views.py:81 .\users\views.py:101 #, fuzzy msgid "username or email" msgstr "9988" 2) It is ok to be fuzzy but my translation of fuzzy

Re: ImportError No module named myapp.views.hometest

forgot to mention i am using django1.1 On Aug 31, 5:35 pm, weiwei <online.service@gmail.com> wrote: > backgroud information: > server: fedora11 > web server : apache 2.2 + mod_wsgi2.5 > > my project location > '/usr/local/django/myproject' > '/usr/l

ImportError No module named myapp.views.hometest

backgroud information: server: fedora11 web server : apache 2.2 + mod_wsgi2.5 my project location '/usr/local/django/myproject' '/usr/local/django/myproject/myapp' in the django.wsgi i have --- sys.path.append('/usr/local/django') sys.path.append('/usr/local/django/myproject')

Re: quick question: how to have *.domainname.com url in django

Could you please expand the process " send all those names to the same Django instance" a little bit more detailed? Thanks On Jul 31, 7:17 am, Javier Guerra <jav...@guerrag.com> wrote: > On Fri, Jul 31, 2009 at 12:26 AM, weiwei<online.service@gmail.com> wrote: &

Re: quick question: how to have *.domainname.com url in django

thanks, i was thinking to have each user have a url as http://username.domain.com/ like http://hiphopo.posterous.com/ On Jul 30, 10:20 pm, Graham Dumpleton <graham.dumple...@gmail.com> wrote: > On Jul 31, 3:09 pm, weiwei <online.service@gmail.com> wrote: > > >

quick question: how to have *.domainname.com url in django

Hello all, I know there are lots of example for how to set http://domainname.com/* url. But how to have http://*.domainname.com url in django? Thanks --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django