This also came into my mind. The point is that one does not want to bother about village records, but one wants to fill the data objects with the result of the query, and this is the difficult part, and where the column order comes in.
I beg to differ. I use databases with a lot of m:n relations. Torque does not support this very well. So I began to use my own sets of select columns which sometimes are distributed over more than 10 tables. There is no way around BasePeer in this case (at least I didn't find one).
Bye, Thomas.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
