On Sun, Jun 28, 2009 at 3:56 PM, Wayne Koorts wrote:
> In your case you'll probably have to drop the id columns and recreate
> them. I'm not sure how Postgres will deal with adding a serial column
> to an existing table, but see how it goes (make backups first of
> course).
It works fine. The on
Fair enough. If that's as bad as it gets for you on Monday morning,
you're doing all right.
Thanks for the help. That sounds like it will address the problem. If
I run into any problems, I'll post them here. So future travelers,
unless I repost, Wayne's plan worked.
Thanks!
On Jun 28, 1:59 pm,
Hi Matt,
> Everything works fantastically, except for when I try to add new
> records to any model in the admin section. When I try to add any
> record, I get a "null value in column "id" violates not-null
> constraint" error.
>
> I'm completely new to postgres, so I imagine this is an error can
> the "serial" column time (
Oops, meant to say "column type". But actually should have said data
type. It's early. On Monday morning. Leeme alone :)
-Wayne
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Djan
Last week I started migrating a project from MySQL over to Postgres to
start toying around with GeoDjango. I ran a dumpall in MySQ, altered
the results and loaded it up into Postgres into tables created by the
syncdb command.
Everything works fantastically, except for when I try to add new
record
5 matches
Mail list logo
