I solved this in an application by creating a separate "sort_name"
field that was strictly used for sorting. Never seen or used by the
user at all. We had a "before_save :build_sort_name" method that
handled all sorts of cases. Wouldn't be too hard to add something
similar for your scenario.
def b
E. Litwin wrote in post #957563:
> On Oct 27, 9:09am, Marnen Laibow-Koser wrote:
>> The easiest way would involve using a separate DB field, so that you can
>> do ORDER BY title, put_at_end.
>
> Wouldn't that have to be ORDER BY put_at_end, title? (assuming
> put_at_end has a value of 0 or 1)
Yes
On Oct 27, 9:09 am, Marnen Laibow-Koser wrote:
> The easiest way would involve using a separate DB field, so that you can
> do ORDER BY title, put_at_end.
Wouldn't that have to be ORDER BY put_at_end, title? (assuming
put_at_end has a value of 0 or 1)
--
You received this message because you ar
3 matches
Mail list logo