If there is no need to reference the objects from outside the group, you
would probably find it a lot more efficient to store the while array
serialized as a byte array.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this
You can serialize a MapString,String property into a byte array to be
stored in the entity
The easiest way to do this would be to use Objectify with the @Serialized
annotation
http://code.google.com/p/objectify-appengine/wiki/IntroductionToObjectify#@Embedded
--
You received this message
You can serialize a MapString,String property into a byte array to be
stored in the entity
The easiest way to do this would be to use Objectify with the @Serialized
annotation
http://code.google.com/p/objectify-appengine/wiki/IntroductionToObjectify#@Serialized
--
You received this message
hi gerald,
thx for your answer but this is the ugliest solution ;) why serializing all
pairs and storing them in one.property it will never be searchable...
using one entity property for every map.entry or using one entity of a key
value pair type, thats the question ;)
schtief
Am
From previous threads, it seems that the datastore prefers few large
entities to more smaller ones - this is also reflected in pricing, you
pay per operation as well as per byte. Storing a Map of Name-Value is
exactly what the datastore is made for.
I did talk to Jeff at Objectify about this
Hi,
Just uploaded a new app. The app requires login via Federated Login. The
first thing that happens is a redirect using the domain parameter appended
to the request :
http://1.koma-software-3.appspot.com/go?domain=koma.be
This gets redirected to :
Sure, thanks Ikai, I should have done this first time around.
When putting the entity (code from around my app stuck together)
log(Storing user {0}, us.getCurrentUser().getUserId());
DatastoreServiceConfig DATASTORE_CONFIG =
DatastoreServiceConfig.Builder.withDeadline(5);
navigating to data store admin on the backend gives me this error :
Error: Not FoundThe requested URL
/_ah/login_required?continue=http://ah-builtin-python-bundle-dot-latest-dot-koma-software-3.appspot.com/_ah/datastore_admin/
was
not found on this server.
--
You received this message
Ah, yes. I saw your original post but couldn't see why it would be
happening - it wasn't an error I came across when getting mine
working.
The code I use for Google accounts (regardless of whether they're apps
or not) is like this...
UserService us = UserServiceFactory.getUserService();
Well, I guess that wont work... I dont want to ordinary google accounts to
have access, only customers who installed my app from the google apps
marketplace.
My URL will be whitelisted and users will never be presented with the login
screen.
So far the theory
Hope someone @ google will
fixed it by providing simply the domain as openid idenitty and NULLs for
the other params :
loginUrl = userService.createLoginURL(request.getOriginalRef().toString(),
null, domain, null);
:-D
--
You received this message because you are subscribed to the Google Groups
Google App Engine for
OK, fixed :
loginUrl = userService.createLoginURL(request.getOriginalRef().toString(),
null, domain, null);
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Excellent but...
a. Why?!
b. Where's the documentation?!
On 4 November 2011 12:49, Koen Maes k...@koma.be wrote:
fixed it by providing simply the domain as openid idenitty and NULLs for the
other params :
loginUrl = userService.createLoginURL(request.getOriginalRef().toString(),
null,
I can now confirm that I do not see this behaviour in production -
only on the dev server.
On Nov 4, 9:01 am, Matthew Jaggard matt...@jaggard.org.uk wrote:
Sure, thanks Ikai, I should have done this first time around.
When putting the entity (code from around my app stuck together)
Thank you, Gerald. I will look for alternative implementations if I
can not call put() many times within a transaction. I am waiting for
Ikai's comments.
J.Ganesan
On Nov 4, 11:02 am, Gerald Tan woefulwab...@gmail.com wrote:
If there is no need to reference the objects from outside the group,
I started from this thread to try these values :
https://groups.google.com/d/msg/google-apps-marketplace-api/HpqT-Bh0BjY/KwevpQVoE30J
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Yeah, that's weird. When you look at http://localhost:8080/_ah/admin, which
user ID is it?
Also ... are those the IDs the dev server is giving you? The dev_server
should be giving pretty simple IDs, if I'm not mistaken.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com
If all 4000 entites are in a single entity group, in theory you can do this
because it counts as a single transactional write. There's a maximum RPC
size of 11mb (implementation detail) so if you trip this, you're in some
trouble - the RPC size include not only the size of the entity but also the
When I view using the datastore viewer, I can only see the e-mail
address of the user (plus the ID of the entity and the encoded key +
write ops).
The User I'm saving is the one that I get from
userService.getCurrentUser() on the dev server and I'm the comparing
the difference in ID from
On Fri, Nov 4, 2011 at 3:56 PM, Ikai Lan (Google) ika...@google.com wrote:
If all 4000 entites are in a single entity group, in theory you can do this
because it counts as a single transactional write. There's a maximum RPC
size of 11mb (implementation detail) so if you trip this, you're in
FWIW you can declare a field @Embedded MapString, anything in
Objectify and this will create a series of native properties in the
low level entity. Ie:
class MyEntity {
@Id Long id;
@Embedded MapString, Long strings;
}
If the map contained { prop1 : 12 } then you could filter by:
Hi,
A simple imap email program fails on appengine. The error message is clear
that appengine does not allow socket classes. Can anyone suggest an option
other than running the service outside appengine?
Our app runs completely on GAE and it's painful to go for webservice from
other cloud
GAE developers,
Anyone tried using java RemoteAPI on local servers and using the JDO object
conversions? like in the example in this chain? I can only work with low
level datastore Entity objects. If anyone has success with usage of JDO
syntax on REmote API, your suggestions are much
This is pretty awesome feature, but did you forget to document it? :)
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine-java/-/z7iXjUGzMLQJ.
To
24 matches
Mail list logo
