# |
Sep 21st 2011, 13:53 |
dakota |
Section58: it's good for 95% of queries. Complex stuff like this is kinda falls over on |
# |
Sep 21st 2011, 13:53 |
Section58 |
i don't think i wanna use it anymore |
# |
Sep 21st 2011, 13:52 |
Section58 |
if its really naturyally like that |
# |
Sep 21st 2011, 13:52 |
Section58 |
i am not happy with that contain |
# |
Sep 21st 2011, 13:52 |
Section58 |
something like that |
# |
Sep 21st 2011, 13:52 |
dakota |
Section58: school project? |
# |
Sep 21st 2011, 13:49 |
carichardson |
I'm switching from php sessions to database sessions right now, created the cake_sessions in my database, updated the core.php file, but I don't see anything saving in cake_sessions table. Anybody know what I'm doing wrong? |
# |
Sep 21st 2011, 13:49 |
Section58 |
it makes it look like i've ust installed a plugin and signed it off |
# |
Sep 21st 2011, 13:48 |
92AAAG7K2 |
Anybody know if it's possible to login a user via a shell? ;) |
# |
Sep 21st 2011, 13:48 |
Section58 |
i try and stay away from cakedc stuff as much as i can |
# |
Sep 21st 2011, 13:48 |
Section58 |
yeah thanks |
# |
Sep 21st 2011, 13:48 |
dakota |
Section58: you know, just something to look at for the future :) |
# |
Sep 21st 2011, 13:48 |
dakota |
Section58: For you filtering, I'm going to point you back to my original suggestion. The CakeDC search plugin is fantastic for anything involving searching. It makes it incredibly easy to build up complex filters |
# |
Sep 21st 2011, 13:48 |
carichardson |
Do any of you use database sessions in cake? |
# |
Sep 21st 2011, 13:47 |
dakota |
~ad7six-advice |
# |
Sep 21st 2011, 13:47 |
dakota |
Section58: Something that helps me tremendously when writing complex queries is to first write out the manual sql query in phpmyadmin (or whatever) and only then convert it to 'cake style' |
# |
Sep 21st 2011, 13:47 |
Section58 |
why do they have to make it so complicated :( |
# |
Sep 21st 2011, 13:47 |
Section58 |
if the query just grabs events then it would be one line |
# |
Sep 21st 2011, 13:46 |
Section58 |
i think the orignal filtering is putting it off |
# |
Sep 21st 2011, 13:46 |
dakota |
but you could do it with joins. |
# |
Sep 21st 2011, 13:46 |
dakota |
containable is basically an intellegent wrapper around $recursive |
# |
Sep 21st 2011, 13:46 |
dakota |
recursion would give you the same result |
# |
Sep 21st 2011, 13:45 |
Section58 |
and not use contains |
# |
Sep 21st 2011, 13:45 |
Section58 |
so maybe i can use recurtion and joins |
# |
Sep 21st 2011, 13:45 |
dakota |
that is true |
# |
Sep 21st 2011, 13:45 |
Section58 |
well normally i have found there are many ways to do the same thing in php |
# |
Sep 21st 2011, 13:45 |
dakota |
) |
# |
Sep 21st 2011, 13:45 |
dakota |
~premature |
# |
Sep 21st 2011, 13:45 |
dakota |
~linkable |
# |
Sep 21st 2011, 13:45 |
dakota |
You could maybe look at linkable, but I'm not sure if it will work like you want. Plus, I've never used it |
# |
Sep 21st 2011, 13:44 |
Section58 |
in my attempt to keep querys down, i apear to have made them worse |
# |
Sep 21st 2011, 13:44 |
dakota |
Section58: yeah |
# |
Sep 21st 2011, 13:44 |
Section58 |
where it should be just 5 |
# |
Sep 21st 2011, 13:44 |
Section58 |
well logically it will do that 1 time for each event matching an artist, cause here is 5 artists in that call, thats 25 lines of sql |
# |
Sep 21st 2011, 13:44 |
dakota |
anyways, to directly answer your question, you'd need to switch to using joins/hasOne binds |
# |
Sep 21st 2011, 13:43 |
dakota |
small times |
# |
Sep 21st 2011, 13:43 |
dakota |
Doesn't look that bad |
# |
Sep 21st 2011, 13:43 |
Section58 |
cause its not so awesome for perforance |
# |
Sep 21st 2011, 13:43 |
Section58 |
how do i go about tidying that up |
# |
Sep 21st 2011, 13:43 |
dakota |
unfortunately |
# |
Sep 21st 2011, 13:43 |
dakota |
Section58: you can't really. It's just how containable works |