On Wed, Feb 17, 2010 at 12:28 PM, ryan ryanb+appeng...@google.com wrote:
On Feb 7, 5:52 pm, Takashi Matsuo matsuo.taka...@gmail.com wrote:
For the time being, you can use following strategy for a workaround.
1) prepare a handler for sending particular mail
2) put this handler into the task
They are faster - use less system resources - but I do not see an effective
way to paginate using the current implementation of cursors which are
forward only unless YOU store the cursor . Given that cursors are
opaque, there is no guarantee if that will work over time.
2010/2/16 Waldemar
Furthermore, it
seems highly probable that as things are, many people will obliviously
write public webapps that take a raw cursor as a parameter. This
could be the new SQL injection attack.
Can you comment a bit more on the security issues?
AFAIK, cursors can not be used to write anything.
I just noticed that the maven repository was updated and all jars that
I need are there. many thanks.
On Feb 14, 6:27 pm, Christian Schuhegger
christian.schuheg...@gmail.com wrote:
Hello,
I understand that this is a prerelease, but is there a maven
repository where I can reference this new
Hi,
what's the advantage of cursors compared to key-based pagination? The
latter at least allows for paginating backwards from any point. Why
don't cursors just build on the same principle?
Bye,
Waldemar Kornewald
On Feb 16, 5:46 pm, Nick Johnson (Google) nick.john...@google.com
wrote:
Hi Andy,
On Feb 4, 3:31 pm, Kyle Heu kyleheus...@gmail.com wrote:
Do the Datastore Cursors solve the 1000 query limit?
actually, we removed the 1000 result limit independent of cursors. you
can now fetch or iterate more than 1000 results, no cursor needed.
On Feb 5, 11:04 am, alf alberto@gmail.com
On Feb 7, 5:52 pm, Takashi Matsuo matsuo.taka...@gmail.com wrote:
For the time being, you can use following strategy for a workaround.
1) prepare a handler for sending particular mail
2) put this handler into the task queue in a transactional manner
exactly! we actually don't even consider it
On Feb 8, 1:33 pm, Stephen sdea...@gmail.com wrote:
What are the performance characteristics of cursors?
good question! we'll address this in the docs, but for now...
The serialised cursor shows that it stores an offset. Does that mean
that if the offset is one million, one million rows will
hah. ryan, meet groups. groups, meet ryan. that Newer link at the
bottom is really useful. it shows all these extra messages that you
don't see at first, sometimes even ones that have already said what
you're about to say. so useful! :P
On Feb 16, 7:28 pm, ryan ryanb+appeng...@google.com wrote:
On Feb 10, 3:10 am, Nick Johnson (Google) nick.john...@google.com
wrote:
The cursor format is internal, and it's not really amenable to being parsed
like this, since it will vary depending on the type of query you're
executing.
+1. the cursor format is an implementation detail. you definitely
Hello,
I understand that this is a prerelease, but is there a maven
repository where I can reference this new SDK? I did not find it at:
http://maven-gae-plugin.googlecode.com/svn/repository/com/google/appengine/
--
You received this message because you are subscribed to the Google Groups
2010/2/9 Stephen sdea...@gmail.com
I'm asking if it's wise to store it as a query parameter embedded in a
web page.
You're right that it's unwise. Depending on how you construct your query, a
user could potentially modify the cursor they send to you to return results
from any query your
Will we be able to construct our own cursors much the same way that we are
able to construct our own Datastore keys (Key.from_path())?
Also along the same lines, will we be able to deconstruct a cursor to get
its components (offset, start_inclusive etc.), as we can now do with keys (
key.name(),
Hi Nickolas,
2010/2/9 Nickolas Daskalou n...@daskalou.com
Will we be able to construct our own cursors much the same way that we are
able to construct our own Datastore keys (Key.from_path())?
No, not practically speaking.
Also along the same lines, will we be able to deconstruct a
I'd want to do this so that I could include parts of the cursor (such as the
offset) into a URL without including other parts (eg. the model kind and
filters). I could then reconstruct the cursor on the server side based on
what was passed into the URL.
For example, if I was searching for blog
Hi Nickolas,
2010/2/9 Nickolas Daskalou n...@daskalou.com
I'd want to do this so that I could include parts of the cursor (such as
the offset) into a URL without including other parts (eg. the model kind and
filters). I could then reconstruct the cursor on the server side based on
what was
Does the production cursor string contain information about the app id,
kind, any filter()s or order()s, and (more importantly) some sort of
numerical value that indicates how many records the next query should
skip? If so, and if we could extract this information (and then use it
again to the
If the cursor had to skip entries by using an offset, its performance would
depend on the size of the offset. This is what the current Query.fetch() api
is doing when you give it an offset. A cursor is a pointer to the entry from
which the next query will start. It has no notion of offset.
On
Still, a slightly modified version of the original request does not
seem unreasonable. He would have to formulate his URLs something like
this:
myblog.com/comments/?q=thefirst=1234
or maybe:
myblog.com/comments/?q=theafter=1234
I could see this being really useful, since encrypting (or worse,
In case it wasn't completely clear - 1234 in this example is the
object's id, not an offset.
Jeff
On Tue, Feb 9, 2010 at 9:02 AM, Jeff Schnitzer j...@infohazard.org wrote:
Still, a slightly modified version of the original request does not
seem unreasonable. He would have to formulate his
Didn't find doc about the Support for Custom Admin Console pages ?
Could that means that we can add custom data to Admin Console webapp ?
PS.: Ikai, sorry about the direct message
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to
Didn't find doc about Support for Custom Admin Console pages ?
Is this a way to add our data in the Admin Console Web app ?
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to
The official docs are pending, but here's Nick Johnson to the rescue:
http://blog.notdot.net/2010/02/New-features-in-1-3-1-prerelease-Cursors
--
Ikai Lan
Developer Programs Engineer, Google App Engine
http://googleappengine.blogspot.com | http://twitter.com/app_engine
--
You received this
On Feb 8, 7:06 pm, Ikai L (Google) ika...@google.com wrote:
The official docs are pending, but here's Nick Johnson to the rescue:
http://blog.notdot.net/2010/02/New-features-in-1-3-1-prerelease-Cursors
What are the performance characteristics of cursors?
The serialised cursor shows that it
There is no offset. The protocol buffer stores a start_key and a boolean
denoting if this start key is inclusive or not. The performance of
continuing the fetch from a cursor should be the same as the performance of
the first entities you got from a query.
On Mon, Feb 8, 2010 at 4:33 PM, Stephen
I got beaten to this answer. No, there is no traversal to get to the offset.
BigTable has an underlying mechanism for range queries on keys. Indexes are
essentially a key comprised of a concatenation of application ID, entity
type, column, value. When a filter operation is performed, the
Ah right, Nick's blog does say start_key and not offset. My bad.
Maybe there will be warnings in the upcoming documentation, but my
first instinct was to embed the serialised cursor in the HTML as the
'next' link. But that doesn't look like a good idea as Nick's decoded
query shows what's
A cursor serializes to a Base64 encoded String, so you can store it anywhere
you want to store strings: Memcached, Datastore, etc. You can even pass it
as an URL parameter to task queues.
2010/2/8 Stephen sdea...@gmail.com
Ah right, Nick's blog does say start_key and not offset. My bad.
I'm asking if it's wise to store it as a query parameter embedded in a
web page.
On Feb 9, 12:26 am, Ikai L (Google) ika...@google.com wrote:
A cursor serializes to a Base64 encoded String, so you can store it anywhere
you want to store strings: Memcached, Datastore, etc. You can even pass it
Nick, et al.:
Could we get a pointer or pointers to in-line documentation as related
to query cursors? If this is what it sounds like, it is far-and-away
the biggest and most useful new feature in the SDK, but we need some
hints about how it is used. I've browsed the source code and found
plenty
As I see, this code was added in r93 and it's SDK 1.2.8.
Does it mean you just didn't mention this feature in 1.2.8?
On Feb 4, 3:18 pm, Nick Johnson (Google) nick.john...@google.com
wrote:
On Thu, Feb 4, 2010 at 10:01 AM, Koen Bok k...@madebysofa.com wrote:
Seems like an exciting update!
-
Do the Datastore Cursors solve the 1000 query limit?
On Feb 3, 5:03 pm, Ikai Lan i...@google.com wrote:
Hello App Engine Developers,
As part of our ongoing efforts to improve release quality and
transparency, we will start prereleasing SDKs for early testing. We
hope this gives developers a
and 30 sec time window?
thx.
On Feb 5, 12:31 am, Kyle Heu kyleheus...@gmail.com wrote:
Do the Datastore Cursors solve the 1000 query limit?
On Feb 3, 5:03 pm, Ikai Lan i...@google.com wrote:
Hello App Engine Developers,
As part of our ongoing efforts to improve release quality and
Seems like an exciting update!
- New Grab Tail added to Memcache API
What does this mean?
On Feb 4, 3:07 am, Jason C jason.a.coll...@gmail.com wrote:
I think it's mean to refer to 304 as an error code - it's the best
HTTP response code of all, and think of what a wonderful place the
Internet
On Thu, Feb 4, 2010 at 10:01 AM, Koen Bok k...@madebysofa.com wrote:
Seems like an exciting update!
- New Grab Tail added to Memcache API
What does this mean?
See the inline docs, here:
I believe that the CRON changes are to address this issue:
http://code.google.com/p/googleappengine/issues/detail?id=1261can=5colspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary%20Log%20Component
Can you please explain the new syntax?
Thanks!
--
You received this message because
Finally, Datastore Query Cursors. Thank you.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to
Datastore Query Cursors seem very interesting. Where can we find
documentation (inline or otherwise) on them?
On Feb 4, 7:18 am, Nick Johnson (Google) nick.john...@google.com
wrote:
On Thu, Feb 4, 2010 at 10:01 AM, Koen Bok k...@madebysofa.com wrote:
Seems like an exciting update!
- New
Maybe itsn't best place for this question, but...
Have you any plans to finish an XMPP API with iq/ and presense/
support (http://code.google.com/p/googleappengine/issues/detail?
id=2071)
On Feb 3, 5:03 pm, Ikai Lan i...@google.com wrote:
Hello App Engine Developers,
As part of our ongoing
Very interesting it couldn't some language .mo dialectindependent adds
for instance arabic months some noted should. Easy output enables
arabic months we can display العملية 04 فبراير أهلا، دخول
--
You received this message because you are subscribed to the Google Groups
Google App Engine
Is there any documentation on the new functionality released for
python, specifically datastore query cursors?
On Feb 3, 4:03 pm, Ikai Lan i...@google.com wrote:
Hello App Engine Developers,
As part of our ongoing efforts to improve release quality and
transparency, we will start prereleasing
I think it's mean to refer to 304 as an error code - it's the best
HTTP response code of all, and think of what a wonderful place the
Internet would be if everyone knew how to use it properly! ;)
j
On Feb 3, 4:03 pm, Ikai Lan i...@google.com wrote:
Hello App Engine Developers,
As part of our
42 matches
Mail list logo
