Re: Some questions about the API

Helge Hess <[email protected]>
Newsgroups gmane.comp.cms.opengroupware.xmlrpc.devel
Message-ID <[email protected]>
Werner Schuster wrote:
>>Correct: its unique for the whole database. (unique for a document kind
>>of makes no sense ;-)
> I thought, they might only be unique for a documents of the same type; ie.
> while I could have only *one* Person with Id "123", I could also have a
> Project with Id "123", etc. But that was answered;

Yup. Unique across the whole db.

>>I still don't find the XML-RPC reference on
>>   http://www.opengroupware.org/en/devs/resources/xmlrpc/
>>Where did you get it?
> 
> er... I am not sure whom you're asking, but if its me: I use the
> XML-RPC doc on the SKYRIX website (the link in the OGo developer docs
> section under XML-RPC);

OK. I put that up because I asked Bjoern to put up the documentation on 
the OGo website several weeks ago, but still can't find it :-( - Could 
have been, that it was stored in some other place ;-)

>>I cannot follow here. "startDate", "endDate", "resources" and
>>"companies" should be regular parts of the qualifier section of the
>>fetchspec and "timeZone" should be a hint.
> 
> Hmm... well as I understand it, the fetchSpec (for Account, etc.)
> has a "qualifier" field which holds a query expression as a string;
> whereas the qualifier field for the appointment.fetch argument, is
> a map that contains the fields "startDate", ...;

Yes, this is right. The qualifier for the appointment datasource is not 
a regular qualifier (see my other mail) and can not be "parsed" from a 
string.
You might want to post an enh-bug on this (make apt-qualifier 
'decodeable' from a string).

regards,
   Helge
-- 
http://www.opengroupware.org/

-- 
OpenGroupware.org XML-RPC
[email protected]
http://mail.opengroupware.org/mailman/listinfo/xmlrpc
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.