Malcolm;
Thanks for everything. I was hoping there was a trick here. I am
interested in getting as much efficiency out of this as possible; in
fact, it is queries like this that made me switch away from php due to
sql hang ups. I guess the long lines of code will have to due. Thanks
for the tip
On Tue, 2007-05-29 at 06:56 +, Michael Newman wrote:
> Thanks for the reply and sorry for my vagueness;
>
> Rob: I was talking about really long lines of python. Thanks for the
> heads up about the all. I was just typing off the top of my head and
> still and figuring out python.
>
>
err.. Malcolm--sorry about the typo
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send
Thanks for the reply and sorry for my vagueness;
Rob: I was talking about really long lines of python. Thanks for the
heads up about the all. I was just typing off the top of my head and
still and figuring out python.
Malcom: I suppose that is what I am asking. Is there any simple way
to take
On Tue, 2007-05-29 at 05:20 +, Michael Newman wrote:
> Something that has been bothering me for awhile and I finally just
> decided to post it here because my code work around hits the database
> way too many times.
>
> I am writing a custom view for an application that uses multiple
>
Its hard to tell what you mean by "really long once I start factoring
time and uniqueness". Do you mean really large data sets or really
wide lines in your python file?
If the former, you will probably need to be more specific about what
the long query contains. If the latter, look at chaining
Something that has been bothering me for awhile and I finally just
decided to post it here because my code work around hits the database
way too many times.
I am writing a custom view for an application that uses multiple
categories per story. So I want to lookup stories so that they aren't
7 matches
Mail list logo
