RE: Hairy problem with has_a and has_many

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

Sorry, it should be:

With MySQL, it's also _OK_ if there is a unique key.

john

> -----Original Message-----
> From: Zhuang Li
> Sent: Wednesday, February 23, 2005 12:04 PM
> To: Perrin Harkins; JJ Merelo
> Cc: Cees Hek; cdbi-talk@xxxxxx.xxxxx.xxx
> Subject: RE: Hairy problem with has_a and has_many
>=20
> With MySQL, it's also if there is a unique key.
>=20
> john
>=20
> > -----Original Message-----
> > From: Perrin Harkins [mailto:perrin@xxxx.xxx]
> > Sent: Tuesday, February 22, 2005 10:18 AM
> > To: JJ Merelo
> > Cc: Cees Hek; cdbi-talk@xxxxxx.xxxxx.xxx
> > Subject: Re: Hairy problem with has_a and has_many
> >
> > 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
> >
>=20
>=20