Following the example in the cookbook[1], I moved components into
a base result class, only to discover that cascaded deletion no longer
worked. Apparently, load_components sets the MRO to C3, which
DBIx::Class relies on heavily. Moving those calls out of the
individual result classes caused
On Tue, Jul 24, 2018 at 12:29:29PM +0200, Marco Vittorini Orgeas wrote:
> Have you specified a custom join condition on that relationship which is
> not showed on the posted code? This is straight from the docs:
No.
--
David Cantrell | semi-evolved ape-thing
Disappointment:
n: No results
On 07/24/2018 12:02 PM, David Cantrell wrote:
Hello classy people!
I have a result class that looks like this ...
package Database::Chimera::Result::Serviceplan;
use parent 'DBIx::Class::Core';
__PACKAGE__->table('serviceplan');
__PACKAGE__->add_columns(
id => {
Hello classy people!
I have a result class that looks like this ...
package Database::Chimera::Result::Serviceplan;
use parent 'DBIx::Class::Core';
__PACKAGE__->table('serviceplan');
__PACKAGE__->add_columns(
id => { data_type => 'INT', is_nullable => 0 },
...
