On 10/10/05 5:41 AM, Uwe Voelker wrote: > Cool. Now only 'sort_by' is missing. What about this: > 1. if it's a scalar, use it as it is (use as sql snippet) > 2. if it's a arrayref expand the column as for the 'query' parameter
Did you try it? :) I already do expansion (and sometimes compression to tN aliases) within sort_by strings. As for non-scalar values, I'm still deciding what the best interface is. it's on my list. > So maybe qr/^(\w+)?\.(\w+)(?: (ASC|DESC)?)$/ or something like this, to > detect, if the search order is given. The "data structure" sort-by arg won't require any string parsing, if I can help it. It's going to be more verbose than the string version, so I want it to be unambiguous. Then it'll have one clear advantage, at least. Instead of being "longer and slightly less fuzzy" it'll be "much longer but absolutely explicit." Anyway, I expect the string version to be the most common. -John ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
