Hi,

isn't ":" encoded to "%3A"?
http://www.blooberry.com/indexdot/html/topics/urlencoding.htm

Austin

On Fri, May 30, 2008 at 7:16 AM, Ahmad <[EMAIL PROTECTED]> wrote:

>
> Hey Austin, I submitted my feature, but I face another problem with
> extended properties: I cannot escape the ":" if it occurred on the
> extended property name or value, any help with this?
>
> On May 29, 9:09 pm, "Austin (Google)" <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > Query on extended properties can be done with the extq feed query
> parameter,
> > ie
> >
> > extq=[NAME1:VALUE1][NAME2:VALUE2][NAME3:VALUE3]....[NAMEX:VALUEX]
> > The documentation is not updated yet on this new feature yet, but it is
> > fully functional from the calendar server.  I will update the group when
> the
> > formal
> > documentation is released.
> >
> > Unfortunately, a more complex SQL-like query on extended properties is
> not
> > available.  You may submit a feature request for it -
> >
> > http://code.google.com/p/gdata-issues/issues/entry
> >
> > Hope it helps,
> > Austin
> >
> > On Wed, May 28, 2008 at 12:57 PM, Ahmad <[EMAIL PROTECTED]> wrote:
> >
> > > Hello, till now the documentation says that it is not possible to
> > > query based on extended properties which are in my opinion a very
> > > powerful feature of the calendar API, may be someone should fix this.
> > > My questions is:
> >
> > > Is it possible to query based on something other than name=value, for
> > > example getting values that are larger or smaller than some value? may
> > > be this should be extended to a complete querying language such as
> > > SQL :)
> >
> > > Thanks.
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to