Hehe, ok I see, if it works, don't touch it =) Well, not sure if my database is happy with it, but I certainly am =) I am using sqltap for a bit of profiling, I put profiler = sqltap.start() in the beginning of my function and statistics = profiler.collect() in the end (the function is consisted of those queries and creating an object which I return in json format), and the average time spent for returning 11000+ Definition rows (with those two tables joined) is approx 0.25 sec. Will definitely monitor it and optimize it eventually if needed, but so far seems pretty good...
Thanks for helping, now back to asking another question with a little bit more complicated query which gave me a nice headache yesterday =) On Tuesday, August 26, 2014 7:46:33 PM UTC, Jonathan Vanasco wrote: > > My advice is that if your database is happy with it right now -- just let > it be. i would probably use an event to time this query though, and log it > somewhere. then just check over time to see if the performance degrades > and is worth revisiting. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
