Hi,

Sorry for my ignorance, if this is common knowledge: What is the use case for sorting millions of different measures from different objects?
The only use case i can think of where the sorting would be necessary is lists like "cities in France by size" or "list of cars by fuel/per 100km". Those list do not have millions of entries, and even there you would need some further logic, since the size is not just one single value, there could be multiple values for the size (or fuel consumption) with different sources and for different times. For cars there could be entries by the manufacturer, by some car-testing magazine, etc. I don't see how this could be adequatly represented/sorted by a database only query.

If however this is necessary, i still don't understand why it must affect the datavalue structure. If a index is necessary it could be done over a serialized representation of the value. This needs to be done anyway, since the values are saved at a specific unit (which is just a wikidata item). To compare them on a database level they must all be saved at the same unit, or some sort of procedure must be used to compare them (or am i missing something again?).

Friedrich


On Wed, Dec 19, 2012 at 12:25 PM, Gregor Hagedorn <g.m.hagedorn@gmail.com> wrote:
On 19 December 2012 11:56, Friedrich Röhrs <f.roehrs@mis.uni-saarland.de> wrote:
> I don't understand why 1.6e-8 is absolutly necessary for sorting and
> comparison. PHP allows for the definition of custom sorting functions. If a
> custom datatype is defined, a custom sorting/comparision function can be
> defined too. Or am i missing some performance points?

I believe for performance reasons in many cases sorting needs to be
performed already by the database and supported by an index. -- gregor

_______________________________________________
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l