On Thu, 25 Sep 2014 10:36:31 +0200
Clemens Ladisch <clem...@ladisch.de> wrote:
> > The first question I'd have is: Where are the ordering criteria,
> > and why aren't they in the database? Someone is imposing an order,
> > but the basis for it is not included in the database design.
>
[amusing list omitted] ;-)
>
> If the ordering is specified by someone doing drag&drop in a list, or
> by saying "insert the new entry after *that one*", then there is no
> better ordering criteria than the relative order of the entries.
>
> Of course, such lists tend to be short enough that the implemtation
> does not really matter, and that an always-updated SortOrder would
> work just fine.
Yes, and yes, absolutely. In that case the order is established by the
user, and can be captured by the application as integers, and stored in
the database. The problem is trivial because the number is limited
to what a human being is willing to sort "by hand". And the SQL is
straightforward.
--jkl
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
