I appreciate your help. Thank you.
On Wednesday, September 12, 2012 11:28:44 AM UTC-6, Brian McKeever wrote:
>
> I actually figured it out.
>
> I created a new virtualenv on my development machine and installed the
> requirements to it, and from that virtualenv, syncdb fails to install the
> inv
I actually figured it out.
I created a new virtualenv on my development machine and installed the
requirements to it, and from that virtualenv, syncdb fails to install the
invitationuser table. I guess whoever is in charge of the django-invitation
repository introduced a bug without changing th
lol wtf.
Perhaps the code on the production server isn't fully up to date? Did you
check the database to ensure the table definitely doesn't already exist?
Did you try running "manage.py sql" on the production server to see if the
SQL is printed out for the missing table?
Cal
On Wed, Sep 12, 201
I am not using any database router.
These are my database settings:
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.postgresql_psycopg2',
'NAME': 'my database name',
'USER': 'my admin name',
'HOST': 'localhost',
'PASSWORD' : 'my password'
}
Are you using any sort of custom db router? (look for DATABASE_ROUTERS in
settings).
On Wed, Sep 12, 2012 at 5:05 PM, Brian McKeever wrote:
> On my development machine, upon freshly creating my postgresql database,
> when I run syncdb, it creates two invitation tables -
> invitation_invitationke
On my development machine, upon freshly creating my postgresql database,
when I run syncdb, it creates two invitation tables -
invitation_invitationkey and invitation_invitationuser.
On my production server, upon freshly creating my postgresql database, when
I run syncdb, it only creates invita
6 matches
Mail list logo
