trange, although I'm not familiar with exactly this
>> particular use case. I'm assuming you are referring to multi-table
>> inheritance. Are you certain Django 1.5 wasn't creating these tables? Was
>> it using migrations or South maybe? (Obviously I don't reme
Hello. We're migrating someone else's app that was at Django 1.5.12 and
we're trying to bring it more up-to-date, step-by-step, starting with
Django 1.6.11.
There's an odd thing. There were a bunch of subclasses of a Model class,
that didn't have any database fields. Django wasn't creating nor
> Righty. Glad you got it sorted.
>
> Cheers mate
>
> -Steven Elliott Jr
>
> On Apr 14, 2010, at 5:39 PM, John Abraham wrote:
>
>
>
> > It's definitely a system path / python path problem. I did the brute
> > force method of linking psycopg
It's definitely a system path / python path problem. I did the brute
force method of linking psycopg to the django project directories,
twice, just to be sure:
cd /Website/Django/times
ln -s /opt/local/Library/Frameworks/Python.framework/Versions/2.6/
lib/python2.6/site-packages/psycopg2 ps
pp it can't load psycopg2. I expect
my site-packages or system path got messed up or something but I'm
really having trouble fixing it, since everything works when I invoke
python manually (i.e. not from apache2/modpython).
I'm using Apple's default apache2 installati
I figured this out. I my __unicode__(self) still refered to the
field! Doh!
I changed it, reran syncdb, and restarted the server and it worked.
Not sure if rerunning syncdb was necessary.
--
John
On Feb 1, 12:44 pm, John Abraham wrote:
> Hi.
>
> I changed models.py to remove a fo
Hi.
I changed models.py to remove a foreign key (user_id field in table
Client), and reran syncdb, but now if I try to create a record of that
type in the admin interface I get an error when I try to save a new
object.
Any idea on how to get rid of this error? It seems the admin site is
caching
I get the same error in the admin interface after manually removing a
field from one of my classes. I removed it in models.py and in the
database. The class in question works fine, but for some reason a
dependent class (one that refers to the other with a foreign key) has
it's admin form broken.
8 matches
Mail list logo