Log message #2299223

# At Username Text
# Sep 22nd 2011, 04:38 Section58 excuse the pun
# Sep 22nd 2011, 04:38 Section58 should beable to be the iceing on the cake
# Sep 22nd 2011, 04:38 Section58 will google around for some hardcore join examples
# Sep 22nd 2011, 04:37 Section58 i think, sort of, i wanna use joins for my events/venue results and somehow still use contain for the filtering
# Sep 22nd 2011, 04:37 NetersLandreau but i think you are on the right track when you say to scuttle containable
# Sep 22nd 2011, 04:36 Section58 i can't be too far off, and this query is already 35 lines of time and learning
# Sep 22nd 2011, 04:36 Section58 yeah, thats what i was thinking
# Sep 22nd 2011, 04:36 Section58 i guess its not possible to do a habtm lookup in one query
# Sep 22nd 2011, 04:36 NetersLandreau i think you are so deep into this that to try and use some third-party code/plugin would only be distracting at this point, tbh
# Sep 22nd 2011, 04:35 Section58 or i will never advance with cake
# Sep 22nd 2011, 04:35 Section58 i can have a look at it, but i have been trying to make my own stuff recently
# Sep 22nd 2011, 04:34 Section58 still havn't worked out habtm joins tho
# Sep 22nd 2011, 04:34 NetersLandreau you can do a lot with cakedc's searchable plugin.. i was able to get to perform some pretty miraculous finds with it
# Sep 22nd 2011, 04:34 Section58 then the sql produced could be near perfection
# Sep 22nd 2011, 04:34 Section58 if i am able to split joins in a if (for filtering)
# Sep 22nd 2011, 04:32 Section58 not enough
# Sep 22nd 2011, 04:32 Section58 )
# Sep 22nd 2011, 04:32 Section58 but i would asume that used containble as well
# Sep 22nd 2011, 04:32 NetersLandreau have you been drinking? your speech is slurred ;)
# Sep 22nd 2011, 04:32 Section58 another sujest was to installed the cakedc searchable plugin
# Sep 22nd 2011, 04:31 Section58 its ust preinitble, as its ment to be my job to improve the app, not make it slower
# Sep 22nd 2011, 04:31 Section58 technicly, i could pretend it doesn't make those 25 querys on the end, i now it would cache the first one anyway
# Sep 22nd 2011, 04:30 NetersLandreau yep
# Sep 22nd 2011, 04:30 Section58 i am logically guessing that the way to fix would be to drop the use of contain and use joins for all the relations and matches
# Sep 22nd 2011, 04:29 ddoom I figured out how to print each radio button separately. But now i'm getting a hidden field before each radio button, and it looks like it has the same name so its overriding the values
# Sep 22nd 2011, 04:29 Section58 its the event/venue part that makes it all werid
# Sep 22nd 2011, 04:29 Section58 on the artists controller, they wanna have a paginated list filtered by genre and country.. with the additional infomation about 'Artist next playing in at Event/Venue' in the results
# Sep 22nd 2011, 04:27 Section58 and my mind was blank
# Sep 22nd 2011, 04:26 Section58 i just tryed to think of it now
# Sep 22nd 2011, 04:26 Section58 more than one, cause it would use values from the first
# Sep 22nd 2011, 04:26 Section58 unknown
# Sep 22nd 2011, 04:25 NetersLandreau how many manual queries do you need to run manually to get it done?
# Sep 22nd 2011, 04:24 Section58 but aprrently thats a normal containable feature
# Sep 22nd 2011, 04:24 Section58 but the working version i have with contain isn't optimized enough (it can make up too 25 duplicate querys)
# Sep 22nd 2011, 04:23 Section58 the merging eith ehr orginal filtering is confusing
# Sep 22nd 2011, 04:23 Section58 i sahould probably work on that
# Sep 22nd 2011, 04:23 Section58 not in one line no
# Sep 22nd 2011, 04:23 NetersLandreau Section58: do you have the raw sql you need?
# Sep 22nd 2011, 04:22 Section58 if you know how to put the labeling in right
# Sep 22nd 2011, 04:22 Section58 ddoom: a foreach also might work
# Sep 22nd 2011, 04:21 ddoom Seguer: Doesn't sound like what I want