On Dec 9, 2010, at 3:45 PM, Sibylle Koczian wrote:
> My join table for a n:m relation hasn't got a separate primary key. The
> table just contains the foreign keys referencing the parent tables, and
> the primary key is the combination of both. As far as I know this is
> perfectly permissible, but I can't get my application to work correctly.
> No error messages, but wrong results.
This is a perfect case for database logging. Seeing the actual queries
being called will show where the problem is.
> As soon as I put an autoincrement PK into the table in the SQLite
> version the errors disappear and the application works just like the
> tutorial.
>
> Now I can do one of two things: change the table in the PostgreSQL
> database as well and not try to get composite primary keys to work with
> Dabo. Or try to make my application as short as possible, describe the
> errors and post all of it here.
>
> If Dabo _should_ work with composite primary keys, I'd do the latter. If
> that's unimportant anyway, I'd stop using them.
It should, but since they are not commonly used, there are most likely
places where the code could be improved to handle them. I never use them, so
that code never gets tested by me; I don't believe Paul uses them either. So a
sample app would be a big help in improving the handling of composite keys in
Dabo.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message:
http://leafe.com/archives/byMID/[email protected]
