Thomas Fischer wrote: > Hm, writing SQL is one of the the things that Torque wants to avoid. One > of the reasons for this is portability between databases. Though Torque > is certainly not perfectly portable, it is much better than plain SQL. [...] > So in my eyes, one should think twice before using custom SQL. There are > cases where it cannot be avoided (see below), but I would think twice > before using it.
I second that. It is sometimes surprising what *can* be done with the Torque Criteria. Custom SQL breaks the basic idea of Torque. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
