polettix has asked for the wisdom of the Perl Monks concerning the following question:

Hello Monks! This is surely clearly written somewhere, but I haven't been able to figure out.

I have this example setup:

Table PROJECT id (primary key for the table) ... Table ACCOUNT id (primary key for the table) project_id (reference to ... Table QUOTA id (primary key for the table) account_id (reference to ...

Using belongs_to it's easy to setup quick accessors and SQL magic like this:

Quota->belongs_to(account => 'Account'); Account->belongs_to(project => 'Project');

... which in turn make it easy to get the one project induced by a quota, like this:

my $project_from_quota = $quota->account()->project();

It's also easy to setup a convenience method, of course:

package Quota; sub project { return shift->account()->project() } #... my $project_from_quota = $quota->project();

I have the feeling that this is a bit hackish though, as it does not provide hints for SQL optimizations (like being able to easily prefetch the project when fetching the quota).

Is there any quick way to add that project accessor that also eases the SQL generator life, e.g. for prefetching stuff? Or should I rely upon the convenience method written above, and then put a bit more effort for using prefetch correctly?

I was thinking about has_one but that seems to be confined to direct relationships between two tables, while here I have the ACCOUNT table providing a bridge (that is anyway NOT inducing a many_to_many, as there is only ONE account for a quota, and ONE project for an account, hence ONE project for a quota).

Thanks for any hint!

perl -ple'$_=reverse' <<<ti.xittelop@oivalf

Io ho capito... ma tu che hai detto?

Replies are listed 'Best First'.
Re: DBIx::Class two (or multiple) level has_one
by beech (Parson) on Sep 04, 2016 at 01:29 UTC