[EMAIL PROTECTED] schrieb:
> On Wed, 25 Apr 2007 at 14:24, Diez B. Roggisch wrote:
>> On Wednesday 25 April 2007 13:43, The Alchemist wrote:
>>> I solved it in the following manner:
>>>
>>> queryobject = queryobject.order_by([tableuser.c.name.op("||")
>>> (tableuser.c.surname)])
>> Nice to see how this works, but of course your approach will render any
>> possible optimizations due to indices on the columns useless, as well as
>> putting more load on the DB for the uneccessary concatenation step. But then
>> it's your app, not mine...
>
> He may be being handed that requirement by someone else, or some
> circumstance outside his application, or some other weird circumstance
> in the ap problem domain, you know :). Indeed, I'm curious what kind
> of situation would call for that unusual sorting order...
I wouldn't call the sorting order unusual - first sort after last name,
then first name. but exactly that can be accomplished by using an order
by clause that features several columns. The concatenation is
unnecessary. But obviously that information wasn't too welcome...
Diez
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
