Still no fulltext search?
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/AQOMSH-8ZbkJ.
To post to this group, send email to
From what I've noticed, the auto-generated IDs are only unique across entity
groups in the SDK.
In production, each entity group has it's own set of IDs.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web
How are you fetching the stored entities? Using a query? or get()?
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/ZHd3pXdHp1IJ.
To post to this
I'm interested in dotcloud too, but their pricing isn't properly explained.
Also, the free tier is extremely weak, 10mb of storage, 10mb of memory, wat?
And the tier above free is 99USD per month :S
I wish there was some competition out there, everything is either: in closed
beta, VPS with a
The biggest issue would likely be the database. I strongly recommend you
become very familiar with how GAE's datastore works.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
You are supposed to design tasks with some level of idempotency, there are
cases where tasks are executed more than once, which will also lead to a
fork bomb if not coded properly.
You are supposed to use task names to prevent forks, as task names are
unique, so a task can't be inserted twice
You can use the db.allocate_ids method (I think it's called that, IIRC) to
generate incremental numeric IDs, it uses the same system the db module uses
to assign unique keys, so it scales like a boss.
--
You received this message because you are subscribed to the Google Groups
Google App
I think a lot of people blindly ask for PHP support because they think it
would imply SQL (specifically MySQL) support and be compatible with existing
PHP applications. So even if GAE gets PHP support, I think most of the PHP
users would have a very bad experience due to the datastore.
--
You
I'm guessing images being always uncompressed is intentional, as their data
is already compressed and attempting to re-compress it won't yield much of
an improvement yet requires that the client decompress it. This sort of
thing matters more on weaker devices such as mobile phones.
--
You
You shouldn't need that many shards. IIRC, on a non-HR datastore, each shard
should be able to handle more than 5 updates per second. If you do need a
lot of shards, It's better to use the taskqueue to act as a deferred retry
buffer.
--
You received this message because you are subscribed to
Look into storing the user inside the key (key name), that way you will be
able to very quickly grab the entity from the datastore (without needing to
query).
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send
11 matches
Mail list logo