This sounds familiar. I believe that this was a known problem back in
October. I ran into it on Linux and it was discussed on the list.
Someone came up with some ideas on how to fix it and I have not had
this problem on any recent TG versions. (Come to think of it, I do
believe I ran into this problem while using PostgreSQL though I can't
remember if it was PostgreSQL specific.)
Basically, at the time tg-admin/SQLObject are trying to set up the
join, the 'list' table has not been created yet.
At any rate, I imagine you are ready to move on and start discovering
the wonders of Turbogears. So the expedient "solution" is to hand
create your database tables.
I set up your model and created it using SQLite.
The schema is below, as reported by sqlite3's .schema command. Create
this and leave your model unchanged and TG will never know that it
wasn't created by tg-admin.
Schema:
CREATE TABLE item (
id INTEGER PRIMARY KEY,
value TEXT NOT NULL,
list_id INT
);
CREATE TABLE list (
id INTEGER PRIMARY KEY,
title TEXT NOT NULL,
user_id INT
);
CREATE TABLE user (
id INTEGER PRIMARY KEY,
email TEXT NOT NULL UNIQUE
);
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
