in reply to CDBI segfaults on me->has_a(me)
Check out the Class::DBI docs under the description for 'has_a' and you will see the following:
*NOTE* You should not attempt to make your primary key column inflate using has_a() as bad things will happen. If you have two tables which share a primary key, consider using might_have() instead.
No reason is given why it's a bad thing, but I would trust them on it... Perhaps a read of the code will shed some light as to why this is bad, but I haven't the time. Regardless, this shouldn't segfault... segfaults are always a sign of a bug and if you have the time, you should try and trace it down and submit a bug report. I'd grab the latest perl and test that first though before spending a lot of time on it.
- Cees
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: CDBI segfaults on me->has_a(me)
by perrin (Chancellor) on May 10, 2004 at 15:10 UTC | |
by cees (Curate) on May 10, 2004 at 19:58 UTC |