It's a bug triggered by the fact that the .svn directories are read-only.
If you make those directories writable the problem *should* go away. Please
try that out and let me know.
Thanks,
Max
--
You received this message because you are subscribed to the Google Groups
Google App Engine for
5 put() RPCs plus one more for the commit, although you could use a batch
put to turn this into 1 put() RPC plus one more for the commit. These are
implementation details though. We may at some point just hold on to the
entire mutation until commit time (easy if you're not asking us to generate
JPA 2, JDO 3, unowned relationships, and tons of bug fixes.
https://plus.google.com/102837845875216819095/posts/9U9VFWqhPx7
--
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
We debated this quite a bit internally. To paraphrase the argument that
carried the day:
XG transactions are awesome but they are not true global transactions.
You're limited to 5 entity groups, you're more likely to see partially
applied transactions in global query results, you can get a
Enabling HR locally is described here:
http://code.google.com/appengine/docs/java/tools/devserver.html#Using_the_Datastore
--
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
Hi everyone,
Due to a mix-up, the JDO/JPA jars that are included in the 1.5.5 SDK do *not
*support XG Transactions. If you want to use XG Transactions with JDO or
JPA in 1.5.5 you can download an updated jar
from
I would also point out that it is possible for Java apps to migrate from
Master/Slave to High Replication:
http://code.google.com/appengine/docs/adminconsole/datastoreadmin.html#Copying_Entities_to_Another_Application
Having to create an empty Python version of your app is no doubt clunky and
not
Interesting results! I've run similar tests with writes (put and delete)
and my results indicate that in most situations, multiple async writes will
perform better than one batch sync call. I can't think of any reason this
wouldn't be the case for reads as well. Are your entities all in
There's a big difference between something that is deprecated and something
that isn't getting any new features. JDO/JPA is most certainly not
deprecated. We are making sure it is keeping pace with our new SDK
releases, and we hope to be able to start enhancing it as soon as we can.
There is
Hi Luke,
First the awesome news:
As of 1.4.0, many queries are implicitly asynchronous. When you call
PreparedQuery.asIterable() or PreparedQuery.asIterator(), we initiate the
query in the background and then immediately return. This lets you do work
while the first batch of results is being
Guillaume,
Which FetchOptions class are you looking at? The last update I see to
either of them was back in April and they were backwards compatible changes.
Thanks,
Max
On Fri, Oct 15, 2010 at 5:51 AM, Guillaume Laforge glafo...@gmail.comwrote:
Excellent, thank you!
The instances view is
We refactored the internals of the DatastoreService implementation pretty
heavily in the release we just pushed out but there shouldn't have been any
backwards incompatible changes to the public API. I'm not familiar with
appengine-clj. Does it use reflection to access non-public
, but not with the
CloudCoverLocalServiceTestHelper. Is there a specific version of App
Engine I should be using? I am using 1.3.2.
On Jun 12, 11:57 pm, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
wrote:
This most likely means that your tests aren't
This most likely means that your tests aren't available as part of your
application. Are you certain you uploaded them?
On Fri, Jun 11, 2010 at 11:31 PM, Art art...@gmail.com wrote:
Dear group,
I would like to know how to make CloudCover (http://code.google.com/p/
cloudcover/) work.
At
GAE is currently read-only for scheduled maintenance. I recommend
subscribing to the google-appengine-downtime-notify group if you'd like to
receive notifications of these events:
http://groups.google.com/group/google-appengine-downtime-notify/browse_thread/thread/5302cb6b950ce215
GAE is currently read-only for scheduled maintenance. I recommend
subscribing to the google-appengine-downtime-notify group if you'd like to
receive notifications of these events:
http://groups.google.com/group/google-appengine-downtime-notify/browse_thread/thread/5302cb6b950ce215
exception...
Jerome
On May 5, 3:47 pm, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
wrote:
GAE is currently read-only for scheduled maintenance. I recommend
subscribing to the google-appengine-downtime-notify group if you'd like
to
receive notifications
GAE is currently read-only for scheduled maintenance. I recommend
subscribing to the google-appengine-downtime-notify group if you'd like to
receive notifications of these events:
http://groups.google.com/group/google-appengine-downtime-notify/browse_thread/thread/4857b46e4e6ff0f9
What aspect of the local datastore are you trying to configure that isn't
covered by LocalDatastoreServiceTestConfig()? I don't think you should have
to configure the ApiProxyLocal or the LocalServerEnvironment directly.
On Sun, Apr 25, 2010 at 3:40 PM, mvsoares mavsoa...@gmail.com wrote:
26, 2010 at 1:33 PM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
What aspect of the local datastore are you trying to configure that isn't
covered by LocalDatastoreServiceTestConfig()? I don't think you should have
to configure the ApiProxyLocal
The dev server used to not execute tasks automatically at all but now the
functionality emulates prod pretty closely.
On Fri, Apr 23, 2010 at 6:02 AM, James jamesk...@gmail.com wrote:
Are you seeing this on the dev server or in production? I vaguely
recall reading somewhere that the dev
The difference between 2 seconds and immediate isn't much. How are you
measuring? Do you have logs that show the time at which the task was
enqueued and the time at which it executes?
Thanks,
Max
On Fri, Apr 23, 2010 at 12:31 PM, Fabrizio fht...@gmail.com wrote:
Production.
On Apr 23,
Felipe Quintella Correia felipequintell...@gmail.com
I'll be sure it's on the runtime classpath as soon as I am home.
Thank you
Felipe Quintella
2010/4/22 Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
Make sure appengine-api-labs.jar is on your runtime
Make sure appengine-api-labs.jar is on your runtime classpath.
Max
On Wed, Apr 21, 2010 at 9:00 PM, Felipe Quintella
felipequintell...@gmail.com wrote:
Hello there.
I'm new to Google AppEngine, but I'm already searched and can't find
the answer to my problem.
I am trying to add a task to
What is the value of the delay variable?
On Thu, Apr 22, 2010 at 1:21 PM, Fabrizio fht...@gmail.com wrote:
Hello,
I need to add a task in the TaskQueue. But I need a small delay before
exectution (2 seconds). I use countdownMillis(long) to delay the
execution. But execution starts
Hi Jeff,
Note that DatastoreServiceConfig exposes a withDefaults() method.
FetchOptions has one too but it's package protected. We didn't expose it
because FetchOptions isn't required for many low level datastore calls and
we didn't see why users would want to create one if they didn't plan to
Hi Didier,
I can't say what's going on with your plugin but this is almost certainly a
classpath issue. DatastoreServiceConfig was introduced in 1.3.2 so make
sure you have the appengine-api.jar that shipped with SDK 1.3.2 in your
classpath.
Max
On Thu, Apr 1, 2010 at 4:01 AM, Didier Durand
On Thu, Apr 1, 2010 at 11:43 AM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
Ok, we'll expose that method.
With a public constructor it's very easy to mix up your args, especially
when you have args of the same type. For example, someone is pretty much
The method that can't be found was added in 1.3.2 so, as John says, this is
almost certainly a classpath problem. My guess is that you have an old
version of appengine-api.jar on your classpath somewhere.
On Tue, Mar 30, 2010 at 8:26 PM, Featheast Lee featheast@gmail.comwrote:
I tried to
be much appreciated. If I can provide any
more data for you, please let me know.
Thanks!
David
On Mar 12, 9:37 pm, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
wrote:
Thanks for the report David, this certainly seems suspicious
Please post your model object definitions and the stack trace.
Thanks!
Max
On Sun, Mar 14, 2010 at 8:51 PM, Philip Tucker ptuc...@gmail.com wrote:
If I annotate a dependent 1:many relationship with @Order(mappedBy =
foo), I get a NPE when I try to remove something from the list. When
I
Thanks for the report David, this certainly seems suspicious. There is at
least one memory leak I'm aware of but it's related to transactions so
that's probably not what you're bumping into. Have you tried taking a heap
dump to see what exactly is building up?
On Fri, Mar 12, 2010 at 1:27 PM,
What version of the sdk are you using?
On Fri, Mar 12, 2010 at 1:36 PM, Pavel Byles pavelby...@gmail.com wrote:
Anyone?
On Fri, Mar 12, 2010 at 8:41 AM, Pavel Byles pavelby...@gmail.com wrote:
I'm trying to delete all entities in my datastore but I receive the
following error:
Which version of the App Engine SDK?
On Fri, Mar 12, 2010 at 1:43 PM, Pavel Byles pavelby...@gmail.com wrote:
GWT: 2.0.3
On Fri, Mar 12, 2010 at 4:38 PM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
What version of the sdk are you using?
On Fri, Mar 12
Yes, the limit is 5:
http://code.google.com/appengine/docs/python/datastore/transactions.html#What_Can_Be_Done_In_a_Transaction
On Mon, Mar 8, 2010 at 4:10 AM, JD liva...@gmail.com wrote:
I am enqueuing tasks within a transaction.
tx.begin()
for (int i=0;i10;i++) {
Queue queue =
Oops, that was the python link. Java link is
http://code.google.com/appengine/docs/java/datastore/transactions.html#What_Can_Be_Done_In_a_Transaction
On Mon, Mar 8, 2010 at 10:02 AM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
Yes, the limit is 5:
http
:50 AM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
1) Readable-urls. http://yourapp.appspot.com/users/max versus
http://yourapp.appspot.com/users/192398411324987
2) The datastore doesn't support uniqueness constraints so a user-defined
key is the only
or not, there exists a
class of problems where a user-defined string pk is a necessary part of the
solution.
Regards,
Max
On Mon, Feb 22, 2010 at 1:52 PM, Jeff Schnitzer j...@infohazard.org wrote:
On Mon, Feb 22, 2010 at 1:19 PM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote
Can you please post your model object definitions for Employee and
Department?
Thanks,
Max
On Mon, Feb 15, 2010 at 11:53 PM, sushama sush.khadil...@gmail.com wrote:
import java.util.List;
import javax.jdo.JDOHelper;
import javax.jdo.PersistenceManager;
import
() {
return lse.getPort();
}
public void waitForServerToStart() throws InterruptedException
{
lse.waitForServerToStart();
}
};
}
};
On Tue, Feb 16, 2010 at 9:35 AM, Max Ross (Google)
maxr
, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
wrote:
Hi Will,
You're loading queue.xml from a different location in your unit tests?
This
is a use case I didn't thoroughly consider. I can certainly fix this for
the next release but let me see if I can find
to make
sure a certain function puts x number tasks in a queue that is not
the default. It doesn't load the queue.xml file unless I use your
workaround (then it works great.)
On Feb 16, 10:21 am, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
wrote:
By default
seem to find
it.
On Feb 16, 10:47 am, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
wrote:
I see. In the test environment it looks in . by default so if you
place
queue.xml in the directory from which you're executing the test it should
pick it up.I
();
pm.makePersistentAll(entities); // it throws exception if it compiled
using sdk1.3.1.
tx.commit();
Full source code is here.https://test-gae-j-sdk-131.googlecode.com/hg/
On 2月12日, 午前3:11, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
wrote:
Assuming
http://gae-java-persistence.blogspot.com/2010/02/truth-about-joins.html
--
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,
Subclassing LocalServiceTestHelper and overriding newEnvironment() should
work fine. What does your implementation of newEnvironment() look like?
On Wed, Feb 10, 2010 at 7:35 PM, Krishna krishnacal...@gmail.com wrote:
Ok!
But when I'm using transactions I'm getting:
Assuming a ClassA object with the specified id already exists, the code
you've posted works fine for me. Could you put together a complete example
that demonstrates the unexpected behavior?
Thanks,
Max
On Wed, Feb 10, 2010 at 7:49 PM, vori vori...@gmail.com wrote:
Is it a bug on JDO of SDK
() {
return new TestEnvironment();
}
Thanks,
Krishna
2010/2/11 Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
:
Subclassing LocalServiceTestHelper and overriding newEnvironment() should
work fine. What does your implementation of newEnvironment() look like
...@gmail.comwrote:
You're right!
I refactored my code and forget to annotate the new setUp method with
@Before.
Sorry for taking your time! It works now.
Thanks,
Krishna
2010/2/11 Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
:
Your code looks fine. Are you
Both value-strategy of SEQUENCE and the standalone sequences work. See
http://code.google.com/p/datanucleus-appengine/source/browse/trunk/tests/org/datanucleus/test/SequenceExamplesJDO.java
and
Hi Steve, thanks for bringing this to our attention. We've identified a
problem on our end and we're in the process of correcting it. You're of
course free to continue using an older version of the SDK, but newer
versions are not susceptible to this problem.
Max
On Tue, Feb 9, 2010 at 5:56 AM,
Thanks for the report. This is indeed the same issue. We're testing a fix
now and hope to have this resolved very soon.
Max
On Tue, Feb 9, 2010 at 4:27 AM, paweł majewski swiatloczuli...@gmail.comwrote:
Look similar to
JDO Sequences work, we just haven't publicized them. The DataNucleus docs
should tell you everything you need to know:
http://www.datanucleus.org/products/accessplatform/jdo/sequences.html
IdGeneratorStrategy.INCREMENT is not yet implemented. What are you looking
to use it for?
Max
On Mon,
. for example, Employee.
-Aswath
On Wed, Feb 10, 2010 at 5:49 AM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
JDO Sequences work, we just haven't publicized them. The DataNucleus docs
should tell you everything you need to know:
http://www.datanucleus.org/products
Hi JD,
We released the api for this feature ahead of the backend support so you'll
need to wait for the next release (currently making its way through QA) to
be able to take advantage of transactional tasks. Once the feature is
enabled, tasks that are added to queues when there is an active
Thanks for the report Steve, looks like a bug. The information in the error
message is still relevant though. The datastore does not support real
regular expression matching, but rather just startsWith filters. So, if
your regex can be rewritten to use GrpName.startsWith() then you can use
that
Hi Kemal, thanks for the report. I can reproduce the exception and I can
make the exception go away by removing the column = F_PK attributes from
the @Persistent annotations. I don't yet know why this is causing a problem
but overriding the name of a primary key column doesn't do anything (the
Fixed in trunk
On Tue, Jan 12, 2010 at 12:56 PM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
Sure, glad I could help.
On Tue, Jan 12, 2010 at 12:52 PM, Kemal Dogan kemal.m...@gmail.comwrote:
hi max,
thanks you very much.
On Tue, Jan 12, 2010 at 10:44
I'm sorry to report that we have not yet hooked in support for
ObjectStringConverter. It shouldn't be too difficult though and I can
definitely see how it would be useful. Please file an issue and we'll get
to it as soon as we can.
http://code.google.com/p/datanucleus-appengine/issues/list
By default the kind of the datastore entity is derived from the simple name
of the class, and test.test1.Test.class.getSimpleName() is the same as
test.test2.Test.class.getSimpleName(). This is documented here:
Thanks for the report, looks like a bug. Multiple contains() clauses are
fine but I didn't properly account for the case where one of the clauses is
on the primary key of the object. The fix should be straightforward but let
me see if I can get you a workaround.
Max
On Thu, Jan 7, 2010 at 7:06
, Jan 8, 2010 at 9:48 AM, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
wrote:
Thanks for the report, looks like a bug. Multiple contains() clauses are
fine but I didn't properly account for the case where one of the clauses is
on the primary key of the object. The fix
Issued filed:
http://code.google.com/p/datanucleus-appengine/issues/detail?id=185
On Fri, Jan 8, 2010 at 10:12 AM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
I'm really sorry but I've been unable to construct an equivalent query that
avoids this bug
Congrats on the release Andy!
The App Engine DataNucleus plugin is not going to work out-of-the-box with
DN 2.0 so please wait until we (Google) update our stuff. This is going to
take some time for us but we will get it taken care of.
Max
On Fri, Jan 8, 2010 at 9:44 AM, Rusty Wright
Fixed in trunk.
On Fri, Jan 8, 2010 at 10:31 AM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
Issued filed:
http://code.google.com/p/datanucleus-appengine/issues/detail?id=185
On Fri, Jan 8, 2010 at 10:12 AM, Max Ross (Google)
maxr+appeng...@google.com
Implicit parameters need to be prefixed with a ':'
query.setFilter(dueDate = :beginDateParam dueDate = :endDateParam);
Max
On Tue, Jan 5, 2010 at 10:53 AM, dantuluri pdantul...@gmail.com wrote:
Hi,
I have the following query with inequality operators on a single
property:
query =
It's not implemented. Could you please file a bug?
http://code.google.com/p/datanucleus-appengine/issues/list
Thanks,
Max
On Sun, Jan 3, 2010 at 7:16 AM, Wong lhw...@gmail.com wrote:
SUBSTRING function for JPA is not working.
entityManager.createQuery(SELECT SUBSTRING(v.name, 1, 3) from
http://gae-java-persistence.blogspot.com/2009/12/more-compact-persistencecapable.html
--
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
I'd recommend basing your code on the example here to get something working:
http://gae-java-persistence.blogspot.com/2009/10/creating-bidrectional-owned-one-to-many.html
Then you can start tweaking.
Max
On Wed, Dec 30, 2009 at 3:02 PM, markm208 markm...@gmail.com wrote:
I am thoroughly
their
parents. If you switch em.persist(search) to em.persist(member) you should
be fine.
Max
On Wed, Dec 30, 2009 at 3:22 PM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
I'd recommend basing your code on the example here to get something
working:
http://gae-java
Looks like you're using the JPA Extension annotation. If you're using JDO,
use javax.jdo.annotations.Extension.
On Wed, Dec 23, 2009 at 8:50 AM, Peter Ondruska peter.ondru...@gmail.comwrote:
I have set few properties unindexed like this:
@Persistent
@Extension(vendorName =
Workaround posted to the bug. Thanks!
On Sun, Dec 20, 2009 at 6:22 AM, David Fuelling sappe...@gmail.com wrote:
I'm pretty sure my issue is a bug, but upon further reflection I
figured I'd bring it to light here in the discussion groups just to be
sure.
Here's the issue, with test code:
Please note that you can still query a Key primary key using comparison, you
just can't do it the exact way you've written your example:
pm.newQuery(select from Person where key = :p).execute(person.getKey());
On Tue, Dec 22, 2009 at 6:30 AM, Michael Chan hsmc...@gmail.com wrote:
Thanks a
Hi Philip,
IdGeneratorStrategy.SEQUENCE support is implemented on top of
DatastoreService.allocateIds(), which is itself the mechanism that the
datastore uses internally to assign ids. So, all properties of datastore id
allocation apply to SEQUENCE. There is a lot of good information about
as a true sequence, or do I need to
create my own sequence and assign the value myself?
On Dec 21, 9:29 am, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
wrote:
Hi Philip,
IdGeneratorStrategy.SEQUENCE support is implemented on top of
DatastoreService.allocateIds
Hi Laco,
We're actively working on the Cursors feature but it's not finished yet.
The api for this feature went out in the latest SDK but the backend changes
did not, which explains the exceptions you're seeing. Cursors will be
available in our next release, due out early next year.
Thanks,
Max
Try adding @Basic. More info here:
http://code.google.com/appengine/docs/java/datastore/usingjpa.html#Class_and_Field_Annotations
On Tue, Dec 15, 2009 at 11:55 PM, Compi lauwers@gmail.com wrote:
Hey Everyone,
I can't seem to get this working. How do you save and read
Yup, it's a bug. Would you mind filing it in the issue tracker? I'll get
it sorted out for the next release.
Thanks,
Max
On Wed, Dec 16, 2009 at 9:34 AM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
Interesting, let me take a look.
On Tue, Dec 15, 2009
I'd recommend reading this blog post - it contains everything you need to
know to persist a one-to-many with JPA:
http://gae-java-persistence.blogspot.com/2009/10/creating-bidrectional-owned-one-to-many.html
Max
On Wed, Dec 16, 2009 at 2:21 PM, Richard richard.fa...@gmail.com wrote:
Hi guys,
Where is your code that adds the task to the queue? Is it being run during
server initializaiton, perhaps as part of a static block or a LoadOnStartup
servlet?
Thanks,
Max
On Tue, Dec 15, 2009 at 8:27 AM, Millisecond millisec...@gmail.com wrote:
Hello,
I'm just testing out super basic
wondering if that is actually working or
still a pre-release item (didn't see anything in the docs about it).
Thanks!
david
On Dec 10, 11:24 pm, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
wrote:
I've made a backwards-compatible bug fix release candidate available
myself), here is a link
to instructions Max wrote on how to install a new plugin version into
the SDK:
http://code.google.com/p/datanucleus-appengine/wiki/HowToUpdateTheSDKWithANewPluginVersion
Regards,
J5
On Dec 10, 11:59 am, Max Ross (Google)
maxr+appeng...@google.commaxr
of
having multiple parent classes for a given child class. Although, it
would be nice if a child class could have different parent types.
Thanks for all your help Max.
-bryce
On Mon, Dec 14, 2009 at 11:30 AM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
I
pm, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
wrote:
Ok I've got good news for you. I need to do more testing but I think
different parent types for child objects should work fine as long as you
use
list-ordering for your one-to-many relationships, which you
, 2009 at 9:06 PM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
Ok I've got good news for you. I need to do more testing but I think
different parent types for child objects should work fine as long as you
use
list-ordering for your one-to-many relationships
anticipate this being a huge problem, heck I could sort the set after
it gets out of the datastore if I had to using a displayOrder field or
something. I don't want to bog down my performance doing this through
some implicit index.
thanks,
-bryce
On Mon, Dec 14, 2009 at 11:04 PM, Max Ross (Google
Please re-read the thread leading up to your post. The timeout shouldn't
impact the completion of the request on the server. If you're seeing
something different please let me know.
Thanks,
Max
On Thu, Dec 10, 2009 at 10:26 PM, Heyali heyal...@gmail.com wrote:
I am also facing simmilar
Hi Sam,
Please read this section of the docs:
http://code.google.com/appengine/docs/java/taskqueue/overview.html#Task_Queues_and_the_Development_Server
It describes the differences between production task queues and local task
queus and explains how to switch back to the old method of manually
Found and fixed the issue:
http://code.google.com/p/datanucleus-appengine/issues/detail?id=171
On Wed, Dec 9, 2009 at 11:48 AM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
Could you please post all the model objects that are involved in the
example? Looks
I've posted a bug fix release candidate containing this fix here:
http://datanucleus-appengine.googlecode.com/files/appengine-orm-1.0.4.1.RC1.zip
On Thu, Dec 10, 2009 at 11:51 AM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
Found and fixed the issue:
http
I've made a backwards-compatible bug fix release candidate available at
http://code.google.com/p/datanucleus-appengine/downloads/list
The release contains a fix for this issue and also renames the config
property to datanucleus.appengine.allowMultipleRelationsOfSameType
Max
On Thu, Dec 10, 2009
, *not the same instance*, but just
the same type. Is there any other way (besides just using Key
instances) you can think of that would accomplish what I am after?
thanks again,
-bryce
On Tue, Dec 8, 2009 at 7:21 PM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote
Thanks for the report, investigating now
On Tue, Dec 8, 2009 at 2:33 PM, Pierre Lavignotte
pierre.lavigno...@gmail.com wrote:
Hi,
I have a problem when I try to inherit a one-to-many relation ship
from a base entity class.
The following model works fine :
Could you please post all the model objects that are involved in the
example? Looks like SpeciesStats is missing. Also, it would be great if
you could post the code that shows how you populate the Community object
before persisting.
Thanks,
Max
On Wed, Dec 9, 2009 at 11:40 AM, Max Ross (Google
/jdotest you
should execute the test case that is failing for me.
I really appreciate your taking a look at this. I'm looking forward
to getting it working.
-bryce
On Tue, Dec 1, 2009 at 10:15 PM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote
Hi Len,
attempted to deregister a transaction that is not currently registered is
an error thrown by the datastore api when a call is made to commit a txn and
there is no txn to commit. Is it possible you have some path through your
code that would result in calling commit() more than once or
I've filed bug
http://code.google.com/p/datanucleus-appengine/issues/detail?id=169 to track
the problem with non-persistent base classes. I have a fix in the works.
I'll be posting a release candidate with this fix and hopefully a few others
in the next day or two.
Thanks,
Max
On Tue, Dec 8,
On Dec 8, 2009 10:14 AM, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
wrote:
Hi Bryce,
I started digging into you issue and quickly bumped into the Multiple
relationships of the same type bug for which I posted the workaround. Then
I got bogged down with unrelated
Filed http://code.google.com/p/datanucleus-appengine/issues/detail?id=170
On Tue, Dec 8, 2009 at 6:18 PM, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng...@google.com
wrote:
Ok I think I know what's going on. First here's a stripped down version of
your object model with the bare
://groups.google.com/group/google-appengine-java/msg/8f5872b05214...
out.put(com.google.appengine.server_url_key, http://
localhost:8080);
return out;
}
};
A+, Dom
--
On Dec 3, 7:01 pm, Max Ross (Google)
maxr+appeng...@google.commaxr%2bappeng
1 - 100 of 137 matches
Mail list logo
