Thanks Jeff, I'll just try the switch at a later time and see how it
goes. I'm pretty much managing the namespaces already in the code so I
think that shouldn't change much, and it's all server side.

Hugo

On Sun, Jul 24, 2011 at 10:06 PM, Jeff Schnitzer <[email protected]> wrote:
> I can't really tell whether the Key<?> change would be an issue for you - it
> would depend a lot on how you are using namespaces and how you generate keys
> (remote java client?  gwt?  server-side only?).  If you're using the
> "standard" practice of setting namespace *immediately* in a servlet Filter,
> you shouldn't notice any difference... but if you are manipulating
> namespaces in a more complicated way, it's hard to predict.  Namespace is a
> transient field in the native datastore Key, so it behaves... strangely.
> Jeff
>
> On Sun, Jul 24, 2011 at 12:50 PM, Hugo Visser <[email protected]> wrote:
>>
>> Correct, I'm still on 2.2.3 (it's great, thanks!). Would I run into
>> big problems switching to 3.0 because of this? In only one or two
>> instances I ran into the last minute key conversion issue, but I've
>> worked around that with a ObjectifyWrapper which is actually not bad
>> at all. In the spirit of "if it ain't broke..." I haven't switched yet
>> to 3.0.
>>
>> The thing is that we have data in a "main" namespace with historical
>> data in different namespaces. Previously this was all in one namespace
>> and because I want to update that data in a transaction it was in the
>> same entity group.
>> Now that it is crossing namespaces it looks like that can't be done
>> anymore, which is a bit of a pain but not a huge problem for now.
>>
>> Hugo
>>
>> On 23 jul, 21:39, Jeff Schnitzer <[email protected]> wrote:
>> > If you are using Objectify 3.0, the Key<?> is a simple wrapper for the
>> > native datastore Key - with all the same namespace consequences.  In
>> > previous versions, the Key<?> -> Key conversion was done last-minute so
>> > it
>> > would "inherit" the namespace then.
>> >
>> > Jeff
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Sat, Jul 23, 2011 at 5:51 AM, Hugo Visser <[email protected]> wrote:
>> > > Well it appears that the entire key path for an entity group is bound
>> > > to one namespace. I am using Objectify in my app which doesn't have
>> > > the namespace in the keys but when checking out the low level Java api
>> > > that became apparent.
>> >
>> > > On 22 jul, 12:48, Hugo Visser <[email protected]> wrote:
>> > > > Is it anywhere explicitly documented that the ancestor of an entity
>> > > > must have it's key in the same namespace as the entity itself? I'm
>> > > > using namespaces a lot in our app and in production I get an error
>> > > > if
>> > > > I try to do a transactional update of an entity with parent x in a
>> > > > different namespace than the entity that I'm updating.
>> >
>> > > > Is this intentional? If it is, I guess the dev server should also
>> > > > check this, my unit tests pass :)
>> >
>> > > > Hugo
>> >
>> > > --
>> > > You received this message because you are subscribed to the Google
>> > > Groups
>> > > "Google App Engine" group.
>> > > To post to this group, send email to
>> > > [email protected].
>> > > To unsubscribe from this group, send email to
>> > > [email protected].
>> > > 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 [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> 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 [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> 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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to