Interesting idea, and one for the books, but, in this case, the sort order is complicated by nothing being fixed. The primary sort concern is whether I'm grouping priorities of the tickets together or not. If grouped, the priority order is considered first [ order by Priority=0,Priority, ]. If I have an item that is zero priority, it ends up at the bottom of the list. If I'm not grouping, then priority is not part of the sort. After that, and always included, is the order by which I want to see my list by (EventID, Airline, ContactInfo, etc).
.. but I have a thought about that... I'll need to check it out tonight after work or tomorrow.... On Thu, Oct 5, 2017 at 3:13 PM, Jim Morris <j...@bearriver.com> wrote: > What you may be able to do is to use a case statement(s) which uses a > bound variable to either a column or dummy > > E.g > > order by case orderControlValue = 1 then column1 else "" end, ... > > > On 10/5/2017 11:51 AM, Igor Tandetnik wrote: > >> On 10/5/2017 2:45 PM, Stephen Chrzanowski wrote: >> >>> Given the query: >>> >>> select EventID, Airline, ContactInfo,TicketID,CreateDate from tEvents >>> where >>> Resolved=:Resolved order by :OrderBy >>> >>> I wanted to bind :OrderBy with field names >>> >> >> You can't. A bound parameter can only appear where a literal is allowed >> by syntax. Field names you'll have to embed directly into the query. >> > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
