If I know I'm going to have a bunch of joins, is there any harm in me writing one addTable(...) for each (some are outer joins, some are inner, against different tables) vs. creating Join objects on the various tables. It's a matter of letting crossdb do some of the heavy lifting so my code doesn't have to be too smart. Or is this going to result somehow in a very inefficient query.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If I know I'm going to have a bunch of joins, is there any harm in me writing one addTable(...) for each (some are outer joins, some are inner, against different tables) vs. creating Join objects on the various tables. It's a matter of letting crossdb do some of the heavy lifting so my code doesn't have to be too smart. Or is this going to result somehow in a very inefficient query.
addTable is totally fine and it's there to make it easier than doing the Join's like you are saying.