Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

Super Search

( #3989=superdoc: print w/replies, xml ) Need Help??

Help for this page

You can also try using Google's advanced search against PerlMonks.

Reset search form

Match text containing
(separate strings with -- default is spaces)
titles against above.

Please be patient after submitting your search.

Match titles containing
(separate strings with -- default is spaces)

authors
(use "[one] [two]" to list multiple authors)
(Searching by author doesn't work for Categorized Questions and Answers yet.)

Search ,
starting at - - .

Search
the following sections:

Skip text containing
(separate strings with -- default is spaces)
(Does not exclude based on titles)

Skip titles containing
(separate strings with -- default is spaces)






parent node's author
(use "[one] [two]" to list multiple authors)
(This doesn't work for Categorized Questions and Answers yet.)

Please be patient after submitting your search.

Log In?
Username:
Password:

What's my password?
Create A New User
Chatterbox?
[Corion]: erix: Yeah, I just found that it has no documentation at all on how to circumvent/ eliminate "1+n SELECTs" by building a local hash... I guess I have to make ->has_many do the hash lookup instead of doing the SQL query. But as the problem ...
[Corion]: ... has only manifested itself so far through the puzzled questions of other bystanders, I won't go deeper at this time. But the DBIx::Class documentation could well do with a document on how to make "it" (that is, ORMs in general) faster ;)
[Corion]: I find that DBIx::Class, like most ORMs makes things easy until they become performance critical and then makes it horribly hard to change things because the design is highly inflexible if you don't already know about the problems of 1+n :-/
[choroba]: that's why I don't like similar libraries. They pretend you don't have to learn SQL, but in the end, you have to learn how SQL plus to overcome their own limitations
[Corion]: "Just write the proper SQL beforehand" is of course the appropriate solution, but if you did that, you wouldn't/couldn't use DBIx::Class either. At least not in an obvious (to me) way.
choroba scratches a "how"
[Corion]: choroba: Exactly... But maybe that's just because I'm old and grumpy ;)
[Corion]: But maybe that could also be a nice talk, how to restructure your DBIx::Class-based app to remove 1+n-style query patterns
[Corion]: In theory, that should be easy because you should have the "where" clause from part 1 of the patterns and then do the corresponding single select using that where clause to select all rows in one go for the n other parts.
[Corion]: But in practice I don't see any obvious places documented in DBIx::Class where one would do that and then just feed hash lookups instead of DB lookups for ->has_many results

How do I use this? | Other CB clients
Other Users?
Others imbibing at the Monastery: (7)
As of 2017-09-25 11:11 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    During the recent solar eclipse, I:









    Results (279 votes). Check out past polls.

    Notices?