Re: Hairy problem with has_a and has_many

[prev] [thread] [next] [Date index for 2005/02/22]

From: Perrin Harkins
Subject: Re: Hairy problem with has_a and has_many
Date: 18:17 on 22 Feb 2005

On Tue, 2005-02-22 at 17:50 +0100, JJ Merelo wrote:
> There's no primary key. And I thought it assumed it was the first one
> only if All was specified.

There has to be a primary key for Class::DBI to work.  It can't make an
object for a specific row in the database if there is no way to refer to
a specific row.

I would guess it's using the first column from Essential in this case.

- Perrin

(message missing)

Hairy problem with has_a and has_many
JJ Merelo 16:00 on 22 Feb 2005

Re: Hairy problem with has_a and has_many
Cees Hek 16:22 on 22 Feb 2005

Re: Hairy problem with has_a and has_many
Joss Shaw 16:24 on 22 Feb 2005

Re: Hairy problem with has_a and has_many
JJ Merelo 16:50 on 22 Feb 2005

And now with ContextualFetch
JJ Merelo 16:55 on 22 Feb 2005

Re: And now with ContextualFetch
Perrin Harkins 18:15 on 22 Feb 2005

Re: And now with ContextualFetch
JJ Merelo 18:25 on 22 Feb 2005

Re: Hairy problem with has_a and has_many
Perrin Harkins 18:17 on 22 Feb 2005

Re: And now with ContextualFetch
Perrin Harkins 18:41 on 22 Feb 2005

Re: And now with ContextualFetch
JJ Merelo 18:56 on 22 Feb 2005

RE: Hairy problem with has_a and has_many
Zhuang Li 20:03 on 23 Feb 2005

RE: Hairy problem with has_a and has_many
Zhuang Li 20:12 on 23 Feb 2005