>
>
> I'm afraid I don't have any magic solutions. The best approach I can
> suggest is to log the SQL that is being executed (either in the
> Postgres query log or by putting in some debug statements into Django
> to output connection.queries). Then narrow down the statement that is
> causing prob
On Wed, Aug 20, 2008 at 11:26 AM, Chris Moffitt <[EMAIL PROTECTED]> wrote:
> I am seeing this error - http://dpaste.com/72596/ with django trunk (rev
> 8445) when I try to run syncdb using psycopg2 but it works just fine if I
> use sqlite.
>
> Basically I'm getting an error when doing the table in
I am seeing this error - http://dpaste.com/72596/ with django trunk (rev
8445) when I try to run syncdb using psycopg2 but it works just fine if I
use sqlite.
Basically I'm getting an error when doing the table introspection code. I
can see that there's been some refactoring in this area but the S
IGNORE ME!! For some reason best known to my computer and Django it
now works Go figure!
On Jul 4, 10:36 am, allisongardner
<[EMAIL PROTECTED]> wrote:
> I have created my models, validated them etc and looked at the sqlall
> output and everything was fine. However when i went to syncdb my
> d
I have created my models, validated them etc and looked at the sqlall
output and everything was fine. However when i went to syncdb my
database it created 5 of 10 tables but and error on the 6th table
(suddenly found multiple primary keys!) caused the process to stop. I
fixed the problem in my mod
5 matches
Mail list logo
