ake off projection param, the result is as
spected:
offset_group = Clients.all().order('-__key__').fetch(limit=10,
offset=skip_recs)
I do not know if this is a bug in projection queries or they have to be
used in a different way. Please help me. I would like to use projection
queries because
On Monday, June 18, 2012 6:00:23 PM UTC-6, Marce (Google) wrote:
>
> - Projection queries are now supported in NDB.
>
>
I have problems with projection queries. If I use them with
.order('-__key__').fetch(limit=20) records returned seems to be only the
even or odd ones. I opened a new discussion
Yes it happens on both servers.
On Monday, June 18, 2012 11:01:08 AM UTC-6, Alfred Fuller wrote:
>
> Does this happen in both the dev_appserver and production?
>
> On Fri, Jun 15, 2012 at 10:28 AM, Christopher Ramírez <
> blindedbythed...@gmail.com> wrote:
>
>>
Thanks barry for pointing me that.
It's a recent answare. I opened the thread last week.
Also, I'm new to google groups and I dont't understand its GUI and
exploring methods quite well.
On Tuesday, June 19, 2012 8:26:40 AM UTC-6, barryhunter wrote:
>
> >
> > I have problems with projection que
It's better for you to use python27 since it is multithreaded. That's means
an instance can handle more than one request simustaneously. Also increase
"default_expiration" when you be ready to deploy to the public your
website. default_expiration: "7d" (7 days) is a good value.
On Tuesday, Ju
xplanation.
> The other thing to check would be if the missing records have values for
> the properties specified in the projection.
>
> Rgds
>
> T
>
> On Tuesday, June 19, 2012 10:35:32 PM UTC+8, Christopher Ramírez wrote:
>>
>> Yes it happens on both servers.
&g
No as I remember.
How can I rebuild an Index?
On Wednesday, June 20, 2012 2:53:12 AM UTC-6, timh wrote:
>
>
>
>
>> I just added a few more records. The new ones appear without trouble.
>> Missing records seems to be the ones saved before the projection index was
>> created.
>>
>>>
>
> If
ed.'
> In this case, the old entities will remain unindexed, while new entities
> will be indexed. The only way to fix this is to re-write the old entities
> (as switching the indexing of a property is a schema change, and the
> datastore does not manage your schem
I'm using db.
On Tuesday, June 19, 2012 2:03:23 PM UTC-6, Guido van Rossum wrote:
>
> On Tuesday, June 19, 2012 7:22:15 AM UTC-7, Christopher Ramírez wrote:
>>
>> On Monday, June 18, 2012 6:00:23 PM UTC-6, Marce (Google) wrote:
>>>
>>> - Projection queri
I know that Search service is not stable enough, so this is just a kind of
bug report.
I've been playing with Search API. Looks amazing! But I noticed it return a
record twice when it meet more than one search filter. For example:
results = index.search(
search.Query(
query_string =
I know that Search service is not stable enough, so this is just a kind of
bug report.
I've been playing with Search API. Looks amazing! But I noticed it return a
record twice when it meet more than one search filter. For example:
results = index.search(
search.Query(
query_string =
Thanks for your contribution Liya!
Have all the basics a modern web apps needs, including REST API's.
On Tuesday, August 28, 2012 4:06:53 PM UTC-6, Ilya Bagrak wrote:
>
> While building Turn-O-Phrase (http://turn-o-phrase.com) and LinkPeelr (
> http://linkpeelr.appspot.com) on GAE, I realized tha
There are some Cloud services that through a HTTP API allow you to do
conversions and/or OCR.
On Monday, September 3, 2012 7:48:55 AM UTC-6, Sarvesh wrote:
>
> I was counting on the Conversion API for GAE hosted OCR. Too bad it is
> being taken down. Is there a way I can avoid a separate hosting
13 matches
Mail list logo
