This sounds like the same problem I'm having. See my post on "VERY poor
performance."
What's happening is that Maypole is sucking down every row in the
account table to fill the $classmetadata->{cgi} structure. (see
http://maypole.simon-cozens.org/doc/View.html#What_Maypole_provides_to_a_template).
I'm hoping the Maypole gods already have a solution for this problem... ;)
Matt Adams wrote:
> Hi:
>
> This may actually be a Class::DBI question but I'm curious to know how
> to convince Maypole to use Class::DBI differently. I've played with
> Maypole a bit but I'm still trying to get my head around how it does
> some things.
>
> I've got a couple tables, account and contact, where each contact
> has_a account.
>
> In my test database, there 3 contacts and some 7000 odd accounts. My
> problem is that whenever I go to display the current account
> preferences via
>
> sub preferences :Exported {
> my ($self, $r) = @_;
> $r->{objects} = [ $r->{user} ];
> }
>
> something in the Maypole framework looks up every possible account
> which takes a very long time. It does manage to stringify
> contact.accountCode to account.accountName properly, but in some cases
> (like when preferences are displayed) I'd really like Maypole to look
> up the single related account record, not every account record in the
> table.
>
> Is this possible? What should I be looking at to override Maypole's
> default behaviour?
>
> I'd really appreciate any comments or suggestions, even if I'm
> completely lost.
>
>
> Thanks in advance,
>
> Matt
_______________________________________________
maypole mailing list
maypole at lists.netthink.co.uk
http://lists.netthink.co.uk/listinfo/maypole
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:56 GMT