Hi,
Perhaps not directly related to your question. But java.util.Date is mostly
deprecated and it is advised to use Calendar API. I believe that is
synchronized.
Thanks
Hari
2010/7/22 Ikai L (Google)
> It should just be whatever the date is on the current instance. In general,
> do not ever r
Hi Ikai,
Sorry to bug you, I didn't quite follow - reworded here:
I *do* need an index on the timestamp field because I want a desc filter.
This ordering may not exactly be the insertion order, but pretty close. If I
wanted to present the objects by real insertion order, I'd need an
additional in
You'll need an index no matter what, as if you did this, you'd need Key
descending. Note that this may not be exact insert order but it'll be pretty
close. This seems to save an index, though, as doing it another way requires
both ascending and descending indexes.
On Wed, Jul 21, 2010 at 5:52 AM,
Cool, if you structure your entity class like this though:
class Entity {
List tags;
String foo;
}
how are you going to query which Entity instances match a given tag? I think
that all the tags need to be indexed so your query statement can find them -
I'm not 100% sure
We don't have an ETA yet. We'll announce it when it's ready.
On Mon, Jul 19, 2010 at 11:08 AM, pac wrote:
> In Alfred Fuller's presentation (http://www.youtube.com/watch?
> v=ofhEyDBpngM&feature=channel), he mentioned that limit of 5000 list
> items and need for number of composite indexes for l
Can you start the transaction before you do the fetch? The way you're
writing it won't result in what you want to do.
If that still doesn't work, just retrieve a new instance of the
PersistenceManager. This is cheap so it won't cost you significant
additional CPU.
On Mon, Jul 19, 2010 at 5:59 AM,
There's no single sign on capability yet, but if you use OpenID, the use
experience can come pretty close.
On Mon, Jul 19, 2010 at 3:27 AM, Just wrote:
> Hi,
>
> is it possible to share the session between a google apps domain and
> appspot.com?
> I wanted to use the ssl of appspot.com for secur
It should just be whatever the date is on the current instance. In general,
do not ever rely on dates to be synchronized. Clock skew is a reality of
distributed computing, and you'll have to work around it. What exactly is
the problem you're trying to solve?
On Sun, Jul 18, 2010 at 11:23 PM, Marcu
Looks okay to me. You might want to post better reproduction steps:
http://www.softwaretestinghelp.com/how-to-write-good-bug-report/
On Fri, Jul 16, 2010 at 3:45 PM, karasu kuro wrote:
> app:
> http://easyalarm97531.appspot.com
> works fine in IE but not in Firefox and Safari.
>
> IE version:6.
Mark,
Thanks very much for this - it's useful. I'm slowly getting used to
this non-relational way of thinking.
The count of the tags doesn't need to be 100% accurate, as it will
only be used to approximate how many entries exist for a given tag -
the tag cloud aim is to show tags associated with
Hello again,
I cannot give you straightforward answer,
try to do as little as possible. Create simple entity,
try to create new, delete some by key, createIfNotExists and similar
DAO methods. Do not put any nontrivial logic to this DAO.
Also make sure you entities have "right" key type and such,
Hi!Marcus, now I use your pattern for transactions:
The code of the method:
public void crearPartido(Long idEqLocal, Long idEqVisitante, Date
fecha,
Fecha fechaAgreg, String resultado, String hora,Long
idTorneo){
PersistenceManager pm =
JDOHelper.getPersi
Seems for conditions, they are same, for orderings, they are not same.
On Jul 21, 8:45 am, Robert Lancer wrote:
> No they are not, that would actually create two indexes even though
> your queries against these indexes might be fairly interchangeable.
>
> On Jul 20, 6:57 pm, Tapir wrote:
>
>
>
>
so vacuum_indexes is really needed, right?
On Jul 21, 11:44 am, Didier Durand wrote:
> Yes, it will need more processing: each new / updated / deleted entity
> will be reflected in each of those indexes.
>
> Lots of details
> athttp://code.google.com/appengine/articles/index_building.html
>
> di
Hey John, thanks for the reply
twig looks interesting but im not using JDO, like i mentioned in my
post.
Also, im not trying to get this specific code to work, im trying to
get help on finding the best way to build entity's that would work
with my intended behavior (mentioned in my first post).
If
Thanks everyone for all your answers, case closed :)
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google
The BlobstoreService recently added support for serving partial byte
ranges from a blob. When this method is invoked the response is
generated with a HTTP 206 (Partial Content) status code. So it looks
like app engine assumes that it is always serving a Range request in
this case.
However, in my c
On 22 Jul 2010, at 02:53, dmetri333 wrote:
private List friends = new ArrayList();
You cannot have direct references for unowned relationships in JDO-GAE.
Twig is the only datastore interface I know of that does allow this
http://code.google.com/p/twig-persist/
--
You received thi
I watched the video and im still having some trouble, A lot of his
examples where in python while im using JAVA/JPA, also i may be having
trouble pulling myself away from the idea of rational dbs
It may be the way im structuring my Entities.
my classes are below, It currently doesn't work in app
Using the native API the is Query.setKeysOnly() that "Makes this query
fetch and return only keys, not full entities."
http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/datastore/Query.html#setKeysOnly()
Is this what you are looking for?
On Jul 21, 5:21 am, TL wrote:
Hi, I created a new app and I want to fill it with data from an old
django app using csv files.
The Java app is like:
@PersistenceCapable(identityType = IdentityType.APPLICATION)
public class Callerid {
@PrimaryKey
@Persistent(valueStrategy = IdGeneratorStrategy.IDENTITY)
Using the native API the is Query.setKeysOnly() that "Makes this query
fetch and return only keys, not full entities."
http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/datastore/Query.html#setKeysOnly()
Is this what you are looking for?
On Jul 21, 5:21 am, TL wrote:
It seems that when deploying the .jar file used by your application are not
being uploaded to the server in GAE.
so, as I alredy told you the only thing that could be causing this error (at
least the one I know) is the lack of the .jar files (libraries) in the right
Directory I mean, war/WEB-INF/li
Actually, the App Engine 1.3.5 SDK has been packaged with the Google Plugin
for Eclipse. The reason that it does not come up when you use "Check for
Updates" is because we change the feature id of the SDK bundle for each
release (to prevent Eclipse from removing "features" that it thinks are
unused
Turns out that one needs to download the latest version of the sdk and
configure eclipse it:
http://code.google.com/eclipse/docs/using_sdks.html
@Hari,
The update will not get you the latest version of GAE because the
latest version of the plugin uses an older version of GAE.
Regards,
Navaneeth
Hi,
I'm creating records of a user's actions. When I fetch these records,
I only ever want them sorted in reverse chronological ordering (the
order they were inserted into the datastore). Does app engine by
default return records in this order? I'm trying to avoid having to
keep an extra index on
I probably have a naive understanding of what you're doing, maybe
explain a little more, but to me it looks like this:
class TagCounter {
int count;
String label; // primary key, unique tag name.
}
class Entity {
String tag;
String foo;
}
whenever
Hi,
Here the "official" details on our question:
http://code.google.com/appengine/docs/java/datastore/queriesandindexes.html#Queries_on_Keys
didier
On Jul 21, 5:21 am, TL wrote:
> I want to run a query and receive a few keys, which I will delete
> afterwards. The problem is that queries return
ok, i've read documentation, but my doubt still remain.
My code work...and has the same structure as you show me.
But , I don't understand the meaning of this warning,
I was worried about the warning level GRAVE.
On 20 Lug, 11:05, Thomas wrote:
> I forgot to metion that If you used jsp as handler
Low level API has a method to do this, in JDO/JPA simply select only
key field in your query.
See
http://gae-java-persistence.blogspot.com/2009/10/keys-only-queries.html
(from Max Ross, GAE team) for details.
Regards
Lorenzo
On Jul 21, 5:21 am, TL wrote:
> I want to run a query and receive a
30 matches
Mail list logo
