Hi guys,
(this might not be the best place to ask this. Let me know if not)
I've got an app currently running on App Engine that takes advantage of the
close integration with Google Accounts so that it is the only way users sign
in. The sign-in process was this:
1. User would click sign
tes the query, and calling get executes it again, so doing it
> that way you're pointlessly duplicating the effort. You're also introducing
> a potential synchronization/concurrency issue.
>
> -Nick Johnson
>
>
>
>
>
>
>
>
>
> On Thu, Apr 7, 2
Hi guys,
Which of the following is more efficient:
Using Query.count(1) to test, then using .get() if there is a result:
---
q = MyModel.all().filter("field =", value)
count = q.count(1)
if count:
result = q.get()
do_stuff(result)
else:
create_entity()
Or just calling .g
Nice work Luke! That game is addicting, haha. Definitely bookmarking that.
--
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-appengine@googlegroups.com.
To unsubscribe from this group, send email
@Calvin: Good point, I'd forgotten about that. The file-concatenation
also an interesting idea, although I'm not sure exactly how I would
implement that.
@Robert: Thanks a million for those links. They're looking quite
helpful.
On Mar 31, 6:11 pm, Calvin wrote:
> Datastore entities are capped
Hi guys,
I'm writing an app that will allow users to sync code between
computers. What would be the best API to use to store these (probably
fairly small) files?
I was initially planning to just use the datastore, but I noticed the
new features of the Blobstore in the latest release, and am now
c
