It is supported in appengine. Every time you set a property in an
Entity (appengine Entity) you can specify if that property is indexed
or not. The partial indexing support just lets you control that on a
per instance basis instead of having the field always indexed or not.
On Fri, Aug 12, 2011 at
Yes, I think it is 10. You can delete old versions so you can upload
new ones, but you can only have a limited number at a time.
On Sat, Jul 17, 2010 at 9:42 AM, aswath satrasala
wrote:
> I am planning to update the application every month. Hence, I want to give
> a different version no for the
There was recent discussion about dependencies (valid for Objectify or any
datastore based impl.) but the eclipse plugin question has not been
answered well.
http://groups.google.com/group/objectify-appengine/browse_thread/thread/d464550b97cee2e3/45c70bea305822fd
I suspect that if you enable th
I appreciate your concern for Objectify staying clean, and consistent.
It *is* good to have frameworks that offer different feature sets and
ways in which they implement them.
On Sun, Mar 14, 2010 at 4:27 AM, John Patterson wrote:
> On 13 Mar 2010, at 11:00, Jeff Schnitzer wrote:
>>
>> since you
Nacho, this may be a silly question, have you used the datastore api
or app-engine?
On Fri, Mar 12, 2010 at 2:19 PM, Nacho Coloma wrote:
>> Because the datastore has no schema the interfaces need to define the schema
>> themselves - as Java objects and some annotations. So if you are already
>>
12 Mar 2010, at 13:01, Scott Hernandez wrote:
>>
>> We have a different idea about live systems and managing
>> upgrades/deployments. To answer the question below, you can always
>> upgrade the data in place because you will always need a way to load
>> that data int
Okay, time to chime in. There are some pretty different philosophies
driving these frameworks.
On Fri, Mar 12, 2010 at 4:56 AM, John Patterson wrote:
>
> On 12 Mar 2010, at 05:45, Jeff Schnitzer wrote:
>
> How, in Twig, do you rename a field?
>
> I'm glad you brought this up. I've found simple r
As I understand it, you never need (or can) prefix you appid to the
key. If you could it would open up the option to get data from other
appids, and that is not possible. That is also a huge security hole,
if it existed :(
You are correct that you need to include the full ancestry to define
the ke
There is some interesting stuff in the release, but I've browsed the
Global Transaction stuff and I'm a little scared.
(http://sites.google.com/site/slim3appengine/slim3-datastore/transactions/global-transaction)
It seems that in the code it writes out a task in a queue to close the
commits, possi
Guillermo,
Taskqueue items can only be 10K
(http://code.google.com/appengine/docs/java/taskqueue/overview.html#Quotas_and_Limits).
The basic idea is that if you have more data than that you put it into
an entity (in the data-store) and have the task pull it out and
process it. It might be that you
I'm pretty sure the "your datastore is empty" message on the admin
data viewer pages doesn't mean that his query, in his application
code, returned no results.
While I don't disagree with you that the data is still in there I'm
pretty what you just described is documented in the behavior of
indexe
It is very simple to know if you need to use google apps or not.
Here is the article about it:
http://code.google.com/appengine/articles/auth.html
1.) Do you want to authenticate users from a specific google apps
domain? (Note: Saying yes will exclude gmail and general google
accounts)
2.) Do you
I got a read error when I tried running with my existing (v1.3.0)
data-store file; I created a new one (by renaming the old one) and
restarting. I suspect the internal format is different and the old
format cannot be read. Whether this is by design or a bug is another
question.
On Tue, Feb 23, 201
If you would like a very simple interface to the app engine datastore
(not JPA/JDO) then Objectify might be for you. It doesn't sound like
you need to use JDO/JPA. Here is an example of exactly what you want:
http://code.google.com/p/objectify-appengine/wiki/IntroductionToObjectify#Basic_Operations
To summarize the issue, you cannot search for a null (list) if you
store a null value in any instance of that (list) property. This is
due to the way indexing is done for lists/arrays in the datastore.
The short answer is no. You will have to store another property as a
marker that you have a null
http://code.google.com/p/objectify-appengine
(it seems it got truncated from John's message)
On Tue, Feb 2, 2010 at 10:32 AM, John Patterson wrote:
> You can check out Twig or Objectify which all aim to do what you are asking
> about.
>
> Twig is higher level - more like an Object database built
You can try the getTail(int) method but I don't think that will do
what you want. It is a destructive operation and will cost you
bandwidth and time.
http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/memcache/MemcacheService.html
On Tue, Jan 26, 2010 at 9:01 AM, John Patt
The docs here seem to indicate that dequeuing happens at 5/sec
(default and 10 max).
http://code.google.com/appengine/docs/java/taskqueue/overview.html
On Oct 27, 8:41 am, James Cooper wrote:
> Hi there,
>
> Last night I experimented with task queues to see what level of
> concurrency I could a
18 matches
Mail list logo