Re: [google-appengine] GAE/J Low Level API Transaction management.

2010-02-27 Thread Patrick Twohig 
FWIW, it looks like that particular issue is a bug with the local
development server and not on the actual app engine.  I tried it out in my
app and it seems that it finds all objects properly.

Pat.

On Thu, Feb 25, 2010 at 6:24 PM, Jeff Schnitzer  wrote:

> Looks good to me, but I don't work for Google so the only help I can
> offer is starring the issue :-(
>
> Jeff
>
> On Thu, Feb 25, 2010 at 5:44 PM, Patrick Twohig
>  wrote:
> > Jeff,
> >
> > I made an issue regarding it, let me know if my unit test left anything
> out.
> >
> > Thanks,
> > Patrick.
> >
> > http://code.google.com/p/googleappengine/issues/detail?id=2879
> >
> > On Fri, Feb 19, 2010 at 1:16 AM, Patrick Twohig <
> patr...@namazustudios.com>
> > wrote:
> >>
> >> I had that suspicion, but, I wasn't 100% sure.  I wonder if it's an
> issue
> >> that shows up in production or just local datastore.
> >>
> >> Pat.
> >>
> >> On Thu, Feb 18, 2010 at 1:34 PM, Jeff Schnitzer 
> >> wrote:
> >>>
> >>> I just created a unit test for this case (there wasn't one before) and
> >>> sure enough, it fails.  Looks like a bug in appengine.  Create an
> >>> issue, I'll star it.
> >>>
> >>> The failing unit test is the last one in this file:
> >>>
> >>>
> http://code.google.com/p/objectify-appengine/source/browse/trunk/src/com/googlecode/ob
> >>> jectify/test/QueryTests.java
> >>>
> >>> FWIW, our implementation is the ancestor() method:
> >>>
> >>>
> http://code.google.com/p/objectify-appengine/source/browse/trunk/src/com/googlecode/objectify/impl/QueryImpl.java
> >>>
> >>> Javadocs are on the interface class:
> >>>
> >>>
> http://objectify-appengine.googlecode.com/svn/trunk/javadoc/com/googlecode/objectify/Query.html
> >>>
> >>> Jeff
> >>>
> >>> On Thu, Feb 18, 2010 at 11:22 AM, Patrick Twohig
> >>>  wrote:
> >>> > Duly noted.  However, I'm not about to rewrite a bulk of my code over
> a
> >>> > single issue I'm having.  At the time I started this, I hadn't
> realized
> >>> > Objectify existed and tried using JDO which turned out to be a
> gigantic
> >>> > nightmare, so I slimmed it down and wrote my own wrapper similar to
> >>> > Objectify.  Right now the only pressing issue is that ancestor
> queries
> >>> > aren't working as expected and it's driving me nuts.  Could you
> perhaps
> >>> > point me to some source in Objectify that executes an ancestor query
> >>> > that I
> >>> > may be able to see?
> >>> >
> >>> > On Wed, Feb 17, 2010 at 10:05 PM, Jeff Schnitzer <
> j...@infohazard.org>
> >>> > wrote:
> >>> >>
> >>> >> The documentation I wrote up here might help:
> >>> >>
> >>> >> http://code.google.com/p/objectify-appengine/wiki/Concepts
> >>> >>
> >>> >> You might consider using something like Objectify (or Twig, or
> >>> >> SimpleDS, etc) instead of the Low-Level API.
> >>> >>
> >>> >> Jeff
> >>> >>
> >>> >> On Wed, Feb 17, 2010 at 9:23 PM, Patrick Twohig
> >>> >>  wrote:
> >>> >> > Aside from the Javadocs, does there exist any further
> documentation
> >>> >> > on
> >>> >> > the
> >>> >> > GAE/J low-level API.  I've had a handfull of issues with it so far
> >>> >> > and
> >>> >> > I'm
> >>> >> > at a bit of a loss.  I'm having trouble with ancestor queries.
> >>> >> > Specifically, I'm not getting any child entities when I look for
> >>> >> > objects
> >>> >> > with no kind specified and just an ancestor.  However, the
> >>> >> > equivalent
> >>> >> > code
> >>> >> > in python performs as expected.
> >>> >> >
> >>> >> > I was also curious how GAE/J organizes transactions.  From what I
> >>> >> > gather
> >>> >> > in
> >>> >> > the documentation, each transaction is organized in a ThreadLocal
> >>> >> > stack.
> >>> >> > Every time you call DatastoreService.beginTransaction() it creates
> a
> >>> >> > new
> >>> >> > transaction, pushes it on the thread local stack then when it's
> >>> >> > done,
> >>> >> > it's
> >>> >> > popped of.  I was curious if it may be possible to add a method
> that
> >>> >> > can
> >>> >> > provide the current transaction given a particular key somehow.
> >>> >> >
> >>> >> >
> >>> >> > --
> >>> >> > Patrick H. Twohig.
> >>> >> >
> >>> >> > Namazu Studios
> >>> >> > P.O. Box 34161
> >>> >> > San Diego, CA 92163-4161
> >>> >> >
> >>> >> > --
> >>> >> > You received this message because you are subscribed to the Google
> >>> >> > Groups
> >>> >> > "Google App Engine" group.
> >>> >> > To post to this group, send email to
> >>> >> > google-appeng...@googlegroups.com.
> >>> >> > To unsubscribe from this group, send email to
> >>> >> > google-appengine+unsubscr...@googlegroups.com
> .
> >>> >> > For more options, visit this group at
> >>> >> > http://groups.google.com/group/google-appengine?hl=en.
> >>> >> >
> >>> >>
> >>> >> --
> >>> >> You received this message because you are subscribed to the Google
> >>> >> Groups
> >>> >> "Google App Engine" group.
> >>> >> To post to this group, send email to
> >>> >> google-appeng...@googlegroups.com.
> >>> >> To unsubscribe from this group, send email to
> >>> >> google-appengine+unsubscr...@

Re: [google-appengine] GAE/J Low Level API Transaction management.

2010-02-25 Thread Jeff Schnitzer 
Looks good to me, but I don't work for Google so the only help I can
offer is starring the issue :-(

Jeff

On Thu, Feb 25, 2010 at 5:44 PM, Patrick Twohig
 wrote:
> Jeff,
>
> I made an issue regarding it, let me know if my unit test left anything out.
>
> Thanks,
> Patrick.
>
> http://code.google.com/p/googleappengine/issues/detail?id=2879
>
> On Fri, Feb 19, 2010 at 1:16 AM, Patrick Twohig 
> wrote:
>>
>> I had that suspicion, but, I wasn't 100% sure.  I wonder if it's an issue
>> that shows up in production or just local datastore.
>>
>> Pat.
>>
>> On Thu, Feb 18, 2010 at 1:34 PM, Jeff Schnitzer 
>> wrote:
>>>
>>> I just created a unit test for this case (there wasn't one before) and
>>> sure enough, it fails.  Looks like a bug in appengine.  Create an
>>> issue, I'll star it.
>>>
>>> The failing unit test is the last one in this file:
>>>
>>> http://code.google.com/p/objectify-appengine/source/browse/trunk/src/com/googlecode/ob
>>> jectify/test/QueryTests.java
>>>
>>> FWIW, our implementation is the ancestor() method:
>>>
>>> http://code.google.com/p/objectify-appengine/source/browse/trunk/src/com/googlecode/objectify/impl/QueryImpl.java
>>>
>>> Javadocs are on the interface class:
>>>
>>> http://objectify-appengine.googlecode.com/svn/trunk/javadoc/com/googlecode/objectify/Query.html
>>>
>>> Jeff
>>>
>>> On Thu, Feb 18, 2010 at 11:22 AM, Patrick Twohig
>>>  wrote:
>>> > Duly noted.  However, I'm not about to rewrite a bulk of my code over a
>>> > single issue I'm having.  At the time I started this, I hadn't realized
>>> > Objectify existed and tried using JDO which turned out to be a gigantic
>>> > nightmare, so I slimmed it down and wrote my own wrapper similar to
>>> > Objectify.  Right now the only pressing issue is that ancestor queries
>>> > aren't working as expected and it's driving me nuts.  Could you perhaps
>>> > point me to some source in Objectify that executes an ancestor query
>>> > that I
>>> > may be able to see?
>>> >
>>> > On Wed, Feb 17, 2010 at 10:05 PM, Jeff Schnitzer 
>>> > wrote:
>>> >>
>>> >> The documentation I wrote up here might help:
>>> >>
>>> >> http://code.google.com/p/objectify-appengine/wiki/Concepts
>>> >>
>>> >> You might consider using something like Objectify (or Twig, or
>>> >> SimpleDS, etc) instead of the Low-Level API.
>>> >>
>>> >> Jeff
>>> >>
>>> >> On Wed, Feb 17, 2010 at 9:23 PM, Patrick Twohig
>>> >>  wrote:
>>> >> > Aside from the Javadocs, does there exist any further documentation
>>> >> > on
>>> >> > the
>>> >> > GAE/J low-level API.  I've had a handfull of issues with it so far
>>> >> > and
>>> >> > I'm
>>> >> > at a bit of a loss.  I'm having trouble with ancestor queries.
>>> >> > Specifically, I'm not getting any child entities when I look for
>>> >> > objects
>>> >> > with no kind specified and just an ancestor.  However, the
>>> >> > equivalent
>>> >> > code
>>> >> > in python performs as expected.
>>> >> >
>>> >> > I was also curious how GAE/J organizes transactions.  From what I
>>> >> > gather
>>> >> > in
>>> >> > the documentation, each transaction is organized in a ThreadLocal
>>> >> > stack.
>>> >> > Every time you call DatastoreService.beginTransaction() it creates a
>>> >> > new
>>> >> > transaction, pushes it on the thread local stack then when it's
>>> >> > done,
>>> >> > it's
>>> >> > popped of.  I was curious if it may be possible to add a method that
>>> >> > can
>>> >> > provide the current transaction given a particular key somehow.
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Patrick H. Twohig.
>>> >> >
>>> >> > Namazu Studios
>>> >> > P.O. Box 34161
>>> >> > San Diego, CA 92163-4161
>>> >> >
>>> >> > --
>>> >> > You received this message because you are subscribed to the Google
>>> >> > Groups
>>> >> > "Google App Engine" group.
>>> >> > To post to this group, send email to
>>> >> > google-appeng...@googlegroups.com.
>>> >> > To unsubscribe from this group, send email to
>>> >> > google-appengine+unsubscr...@googlegroups.com.
>>> >> > For more options, visit this group at
>>> >> > http://groups.google.com/group/google-appengine?hl=en.
>>> >> >
>>> >>
>>> >> --
>>> >> You received this message because you are subscribed to the Google
>>> >> Groups
>>> >> "Google App Engine" group.
>>> >> To post to this group, send email to
>>> >> google-appeng...@googlegroups.com.
>>> >> To unsubscribe from this group, send email to
>>> >> google-appengine+unsubscr...@googlegroups.com.
>>> >> For more options, visit this group at
>>> >> http://groups.google.com/group/google-appengine?hl=en.
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Patrick H. Twohig.
>>> >
>>> > Namazu Studios
>>> > P.O. Box 34161
>>> > San Diego, CA 92163-4161
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups
>>> > "Google App Engine" group.
>>> > To post to this group, send email to google-appeng...@googlegroups.com.
>>> > To unsubscribe from this group, send email to
>>> > google-appengine+unsubscr...@googlegroups.com.
>>> > For more

Re: [google-appengine] GAE/J Low Level API Transaction management.

2010-02-25 Thread Patrick Twohig 
Jeff,

I made an issue regarding it, let me know if my unit test left anything out.

Thanks,
Patrick.

http://code.google.com/p/googleappengine/issues/detail?id=2879

On Fri, Feb 19, 2010 at 1:16 AM, Patrick Twohig
wrote:

> I had that suspicion, but, I wasn't 100% sure.  I wonder if it's an issue
> that shows up in production or just local datastore.
>
> Pat.
>
>
> On Thu, Feb 18, 2010 at 1:34 PM, Jeff Schnitzer wrote:
>
>> I just created a unit test for this case (there wasn't one before) and
>> sure enough, it fails.  Looks like a bug in appengine.  Create an
>> issue, I'll star it.
>>
>> The failing unit test is the last one in this file:
>>
>> http://code.google.com/p/objectify-appengine/source/browse/trunk/src/com/googlecode/ob
>> jectify/test/QueryTests.java
>>
>> FWIW, our implementation is the ancestor() method:
>>
>> http://code.google.com/p/objectify-appengine/source/browse/trunk/src/com/googlecode/objectify/impl/QueryImpl.java
>>
>> Javadocs are on the interface class:
>>
>> http://objectify-appengine.googlecode.com/svn/trunk/javadoc/com/googlecode/objectify/Query.html
>>
>> Jeff
>>
>> On Thu, Feb 18, 2010 at 11:22 AM, Patrick Twohig
>>  wrote:
>> > Duly noted.  However, I'm not about to rewrite a bulk of my code over a
>> > single issue I'm having.  At the time I started this, I hadn't realized
>> > Objectify existed and tried using JDO which turned out to be a gigantic
>> > nightmare, so I slimmed it down and wrote my own wrapper similar to
>> > Objectify.  Right now the only pressing issue is that ancestor queries
>> > aren't working as expected and it's driving me nuts.  Could you perhaps
>> > point me to some source in Objectify that executes an ancestor query
>> that I
>> > may be able to see?
>> >
>> > On Wed, Feb 17, 2010 at 10:05 PM, Jeff Schnitzer 
>> > wrote:
>> >>
>> >> The documentation I wrote up here might help:
>> >>
>> >> http://code.google.com/p/objectify-appengine/wiki/Concepts
>> >>
>> >> You might consider using something like Objectify (or Twig, or
>> >> SimpleDS, etc) instead of the Low-Level API.
>> >>
>> >> Jeff
>> >>
>> >> On Wed, Feb 17, 2010 at 9:23 PM, Patrick Twohig
>> >>  wrote:
>> >> > Aside from the Javadocs, does there exist any further documentation
>> on
>> >> > the
>> >> > GAE/J low-level API.  I've had a handfull of issues with it so far
>> and
>> >> > I'm
>> >> > at a bit of a loss.  I'm having trouble with ancestor queries.
>> >> > Specifically, I'm not getting any child entities when I look for
>> objects
>> >> > with no kind specified and just an ancestor.  However, the equivalent
>> >> > code
>> >> > in python performs as expected.
>> >> >
>> >> > I was also curious how GAE/J organizes transactions.  From what I
>> gather
>> >> > in
>> >> > the documentation, each transaction is organized in a ThreadLocal
>> stack.
>> >> > Every time you call DatastoreService.beginTransaction() it creates a
>> new
>> >> > transaction, pushes it on the thread local stack then when it's done,
>> >> > it's
>> >> > popped of.  I was curious if it may be possible to add a method that
>> can
>> >> > provide the current transaction given a particular key somehow.
>> >> >
>> >> >
>> >> > --
>> >> > Patrick H. Twohig.
>> >> >
>> >> > Namazu Studios
>> >> > P.O. Box 34161
>> >> > San Diego, CA 92163-4161
>> >> >
>> >> > --
>> >> > You received this message because you are subscribed to the Google
>> >> > Groups
>> >> > "Google App Engine" group.
>> >> > To post to this group, send email to
>> google-appeng...@googlegroups.com.
>> >> > To unsubscribe from this group, send email to
>> >> > google-appengine+unsubscr...@googlegroups.com
>> .
>> >> > For more options, visit this group at
>> >> > http://groups.google.com/group/google-appengine?hl=en.
>> >> >
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> Groups
>> >> "Google App Engine" group.
>> >> To post to this group, send email to google-appengine@googlegroups.com
>> .
>> >> To unsubscribe from this group, send email to
>> >> google-appengine+unsubscr...@googlegroups.com
>> .
>> >> For more options, visit this group at
>> >> http://groups.google.com/group/google-appengine?hl=en.
>> >>
>> >
>> >
>> >
>> > --
>> > Patrick H. Twohig.
>> >
>> > Namazu Studios
>> > P.O. Box 34161
>> > San Diego, CA 92163-4161
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups
>> > "Google App Engine" group.
>> > To post to this group, send email to google-appeng...@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > google-appengine+unsubscr...@googlegroups.com
>> .
>> > For more options, visit this group at
>> > http://groups.google.com/group/google-appengine?hl=en.
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To post to this group, send email to goog

Re: [google-appengine] GAE/J Low Level API Transaction management.

2010-02-19 Thread Patrick Twohig 
I had that suspicion, but, I wasn't 100% sure.  I wonder if it's an issue
that shows up in production or just local datastore.

Pat.

On Thu, Feb 18, 2010 at 1:34 PM, Jeff Schnitzer  wrote:

> I just created a unit test for this case (there wasn't one before) and
> sure enough, it fails.  Looks like a bug in appengine.  Create an
> issue, I'll star it.
>
> The failing unit test is the last one in this file:
>
> http://code.google.com/p/objectify-appengine/source/browse/trunk/src/com/googlecode/ob
> jectify/test/QueryTests.java
>
> FWIW, our implementation is the ancestor() method:
>
> http://code.google.com/p/objectify-appengine/source/browse/trunk/src/com/googlecode/objectify/impl/QueryImpl.java
>
> Javadocs are on the interface class:
>
> http://objectify-appengine.googlecode.com/svn/trunk/javadoc/com/googlecode/objectify/Query.html
>
> Jeff
>
> On Thu, Feb 18, 2010 at 11:22 AM, Patrick Twohig
>  wrote:
> > Duly noted.  However, I'm not about to rewrite a bulk of my code over a
> > single issue I'm having.  At the time I started this, I hadn't realized
> > Objectify existed and tried using JDO which turned out to be a gigantic
> > nightmare, so I slimmed it down and wrote my own wrapper similar to
> > Objectify.  Right now the only pressing issue is that ancestor queries
> > aren't working as expected and it's driving me nuts.  Could you perhaps
> > point me to some source in Objectify that executes an ancestor query that
> I
> > may be able to see?
> >
> > On Wed, Feb 17, 2010 at 10:05 PM, Jeff Schnitzer 
> > wrote:
> >>
> >> The documentation I wrote up here might help:
> >>
> >> http://code.google.com/p/objectify-appengine/wiki/Concepts
> >>
> >> You might consider using something like Objectify (or Twig, or
> >> SimpleDS, etc) instead of the Low-Level API.
> >>
> >> Jeff
> >>
> >> On Wed, Feb 17, 2010 at 9:23 PM, Patrick Twohig
> >>  wrote:
> >> > Aside from the Javadocs, does there exist any further documentation on
> >> > the
> >> > GAE/J low-level API.  I've had a handfull of issues with it so far and
> >> > I'm
> >> > at a bit of a loss.  I'm having trouble with ancestor queries.
> >> > Specifically, I'm not getting any child entities when I look for
> objects
> >> > with no kind specified and just an ancestor.  However, the equivalent
> >> > code
> >> > in python performs as expected.
> >> >
> >> > I was also curious how GAE/J organizes transactions.  From what I
> gather
> >> > in
> >> > the documentation, each transaction is organized in a ThreadLocal
> stack.
> >> > Every time you call DatastoreService.beginTransaction() it creates a
> new
> >> > transaction, pushes it on the thread local stack then when it's done,
> >> > it's
> >> > popped of.  I was curious if it may be possible to add a method that
> can
> >> > provide the current transaction given a particular key somehow.
> >> >
> >> >
> >> > --
> >> > Patrick H. Twohig.
> >> >
> >> > Namazu Studios
> >> > P.O. Box 34161
> >> > San Diego, CA 92163-4161
> >> >
> >> > --
> >> > You received this message because you are subscribed to the Google
> >> > Groups
> >> > "Google App Engine" group.
> >> > To post to this group, send email to
> google-appeng...@googlegroups.com.
> >> > To unsubscribe from this group, send email to
> >> > google-appengine+unsubscr...@googlegroups.com
> .
> >> > For more options, visit this group at
> >> > http://groups.google.com/group/google-appengine?hl=en.
> >> >
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Google App Engine" group.
> >> To post to this group, send email to google-appeng...@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> google-appengine+unsubscr...@googlegroups.com
> .
> >> For more options, visit this group at
> >> http://groups.google.com/group/google-appengine?hl=en.
> >>
> >
> >
> >
> > --
> > Patrick H. Twohig.
> >
> > Namazu Studios
> > P.O. Box 34161
> > San Diego, CA 92163-4161
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-appeng...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com
> .
> > For more options, visit this group at
> > http://groups.google.com/group/google-appengine?hl=en.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appeng...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>


-- 
Patrick H. Twohig.

Namazu Studios
P.O. Box 34161
San Diego, CA 92163-4161

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com

Re: [google-appengine] GAE/J Low Level API Transaction management.

2010-02-18 Thread Jeff Schnitzer 
I just created a unit test for this case (there wasn't one before) and
sure enough, it fails.  Looks like a bug in appengine.  Create an
issue, I'll star it.

The failing unit test is the last one in this file:
http://code.google.com/p/objectify-appengine/source/browse/trunk/src/com/googlecode/objectify/test/QueryTests.java

FWIW, our implementation is the ancestor() method:
http://code.google.com/p/objectify-appengine/source/browse/trunk/src/com/googlecode/objectify/impl/QueryImpl.java

Javadocs are on the interface class:
http://objectify-appengine.googlecode.com/svn/trunk/javadoc/com/googlecode/objectify/Query.html

Jeff

On Thu, Feb 18, 2010 at 11:22 AM, Patrick Twohig
 wrote:
> Duly noted.  However, I'm not about to rewrite a bulk of my code over a
> single issue I'm having.  At the time I started this, I hadn't realized
> Objectify existed and tried using JDO which turned out to be a gigantic
> nightmare, so I slimmed it down and wrote my own wrapper similar to
> Objectify.  Right now the only pressing issue is that ancestor queries
> aren't working as expected and it's driving me nuts.  Could you perhaps
> point me to some source in Objectify that executes an ancestor query that I
> may be able to see?
>
> On Wed, Feb 17, 2010 at 10:05 PM, Jeff Schnitzer 
> wrote:
>>
>> The documentation I wrote up here might help:
>>
>> http://code.google.com/p/objectify-appengine/wiki/Concepts
>>
>> You might consider using something like Objectify (or Twig, or
>> SimpleDS, etc) instead of the Low-Level API.
>>
>> Jeff
>>
>> On Wed, Feb 17, 2010 at 9:23 PM, Patrick Twohig
>>  wrote:
>> > Aside from the Javadocs, does there exist any further documentation on
>> > the
>> > GAE/J low-level API.  I've had a handfull of issues with it so far and
>> > I'm
>> > at a bit of a loss.  I'm having trouble with ancestor queries.
>> > Specifically, I'm not getting any child entities when I look for objects
>> > with no kind specified and just an ancestor.  However, the equivalent
>> > code
>> > in python performs as expected.
>> >
>> > I was also curious how GAE/J organizes transactions.  From what I gather
>> > in
>> > the documentation, each transaction is organized in a ThreadLocal stack.
>> > Every time you call DatastoreService.beginTransaction() it creates a new
>> > transaction, pushes it on the thread local stack then when it's done,
>> > it's
>> > popped of.  I was curious if it may be possible to add a method that can
>> > provide the current transaction given a particular key somehow.
>> >
>> >
>> > --
>> > Patrick H. Twohig.
>> >
>> > Namazu Studios
>> > P.O. Box 34161
>> > San Diego, CA 92163-4161
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Google App Engine" group.
>> > To post to this group, send email to google-appeng...@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > google-appengine+unsubscr...@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/google-appengine?hl=en.
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To post to this group, send email to google-appeng...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>
>
> --
> Patrick H. Twohig.
>
> Namazu Studios
> P.O. Box 34161
> San Diego, CA 92163-4161
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appeng...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] GAE/J Low Level API Transaction management.

2010-02-18 Thread Patrick Twohig 
Duly noted.  However, I'm not about to rewrite a bulk of my code over a
single issue I'm having.  At the time I started this, I hadn't realized
Objectify existed and tried using JDO which turned out to be a gigantic
nightmare, so I slimmed it down and wrote my own wrapper similar to
Objectify.  Right now the only pressing issue is that ancestor queries
aren't working as expected and it's driving me nuts.  Could you perhaps
point me to some source in Objectify that executes an ancestor query that I
may be able to see?

On Wed, Feb 17, 2010 at 10:05 PM, Jeff Schnitzer wrote:

> The documentation I wrote up here might help:
>
> http://code.google.com/p/objectify-appengine/wiki/Concepts
>
> You might consider using something like Objectify (or Twig, or
> SimpleDS, etc) instead of the Low-Level API.
>
> Jeff
>
> On Wed, Feb 17, 2010 at 9:23 PM, Patrick Twohig
>  wrote:
> > Aside from the Javadocs, does there exist any further documentation on
> the
> > GAE/J low-level API.  I've had a handfull of issues with it so far and
> I'm
> > at a bit of a loss.  I'm having trouble with ancestor queries.
> > Specifically, I'm not getting any child entities when I look for objects
> > with no kind specified and just an ancestor.  However, the equivalent
> code
> > in python performs as expected.
> >
> > I was also curious how GAE/J organizes transactions.  From what I gather
> in
> > the documentation, each transaction is organized in a ThreadLocal stack.
> > Every time you call DatastoreService.beginTransaction() it creates a new
> > transaction, pushes it on the thread local stack then when it's done,
> it's
> > popped of.  I was curious if it may be possible to add a method that can
> > provide the current transaction given a particular key somehow.
> >
> >
> > --
> > Patrick H. Twohig.
> >
> > Namazu Studios
> > P.O. Box 34161
> > San Diego, CA 92163-4161
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-appeng...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com
> .
> > For more options, visit this group at
> > http://groups.google.com/group/google-appengine?hl=en.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appeng...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>


-- 
Patrick H. Twohig.

Namazu Studios
P.O. Box 34161
San Diego, CA 92163-4161

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] GAE/J Low Level API Transaction management.

2010-02-17 Thread Jeff Schnitzer 
The documentation I wrote up here might help:

http://code.google.com/p/objectify-appengine/wiki/Concepts

You might consider using something like Objectify (or Twig, or
SimpleDS, etc) instead of the Low-Level API.

Jeff

On Wed, Feb 17, 2010 at 9:23 PM, Patrick Twohig
 wrote:
> Aside from the Javadocs, does there exist any further documentation on the
> GAE/J low-level API.  I've had a handfull of issues with it so far and I'm
> at a bit of a loss.  I'm having trouble with ancestor queries.
> Specifically, I'm not getting any child entities when I look for objects
> with no kind specified and just an ancestor.  However, the equivalent code
> in python performs as expected.
>
> I was also curious how GAE/J organizes transactions.  From what I gather in
> the documentation, each transaction is organized in a ThreadLocal stack.
> Every time you call DatastoreService.beginTransaction() it creates a new
> transaction, pushes it on the thread local stack then when it's done, it's
> popped of.  I was curious if it may be possible to add a method that can
> provide the current transaction given a particular key somehow.
>
>
> --
> Patrick H. Twohig.
>
> Namazu Studios
> P.O. Box 34161
> San Diego, CA 92163-4161
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appeng...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] GAE/J Low Level API Transaction management.

2010-02-17 Thread Patrick Twohig 
Aside from the Javadocs, does there exist any further documentation on the
GAE/J low-level API.  I've had a handfull of issues with it so far and I'm
at a bit of a loss.  I'm having trouble with ancestor queries.
Specifically, I'm not getting any child entities when I look for objects
with no kind specified and just an ancestor.  However, the equivalent code
in python performs as expected.

I was also curious how GAE/J organizes transactions.  From what I gather in
the documentation, each transaction is organized in a ThreadLocal stack.
Every time you call DatastoreService.beginTransaction() it creates a new
transaction, pushes it on the thread local stack then when it's done, it's
popped of.  I was curious if it may be possible to add a method that can
provide the current transaction given a particular key somehow.


-- 
Patrick H. Twohig.

Namazu Studios
P.O. Box 34161
San Diego, CA 92163-4161

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.