[Developers] index of null, default ordering?

[Alec Flett]

That's almost exactly the query that the freebase.com client uses,  
except it uses "-link.timestamp" instead of "link.timestamp" because  
it wants newer things first.

oh, and we don't use "guid", we use "id" - again, guid is discouraged  
in favor of "id" for most things...

Alec


On Feb 28, 2008, at 1:27 PM, Christopher Dummy wrote:

> Thanks for that information.
>
> For the timestamp, is it using  "link": {"timestamp":null} ? Which
> means for any property to get it sorted in the way it is displayed in
> the UI, I would use the following query for the property:
>
>      "/user/cotton/default_domain/broadcast/genre" : [ {
>          "guid" : null,
>          "name" : null,
>          "index" : null,
>          "link" : { "timestamp" : null },
>          "sort" : [ "index",  "link.timestamp"  ]  }
>
>
> On Thu, Feb 28, 2008 at 3:05 PM, Christopher R. Maden <crism at metaweb.com 
> > wrote:
>> Christopher Dummy wrote:
>>> If I ask for the set of properties on an item. What is the default
>>> ordering of those items?
>>
>> It is effectively random.
>>
>> It is actually in the order in which the items are found, which is
>> typically the order in which they were created, but that is not  
>> reliable
>> behavior.
>>
>> The UI sorts by index and by timestamp by default.  Items with a null
>> index have not been explicitly ordered.
>>
>> Hope this helps,
>> Chris
>> --
>> Christopher R. Maden
>> Data Architect
>> Metaweb Technologies, Inc.
>> <URL: http://www.metaweb.com/ >
>> _______________________________________________
>> Developers mailing list
>> Developers at freebase.com
>> http://lists.freebase.com/mailman/listinfo/developers
>>
>
>
>
> -- 
> Christopher Cotton
> Zing/Dell Engineer
> http://zing.net/
> _______________________________________________
> Developers mailing list
> Developers at freebase.com
> http://lists.freebase.com/mailman/listinfo/developers