On Nov 6, 10:37 am, mawei1981 <[EMAIL PROTECTED]> wrote:
> Hi, All
>
> As we know, the database provide a unique key not a primary key to
> support we store some content we do not like redundant, we query some
> content use distinct because we do not want to see redundant record.
>
> So, when I
thanks
On Nov 6, 6:25 pm, dobee <[EMAIL PROTECTED]> wrote:
> On Nov 6, 10:37 am, mawei1981 <[EMAIL PROTECTED]> wrote:
>
> > Hi, All
>
> > As we know, the database provide a unique key not a primary key to
> > support we store some content we do not like redundant, we query some
> > content use di
Can't this be done with a carefully constructed key_name?
On Nov 6, 2:25 am, dobee <[EMAIL PROTECTED]> wrote:
> On Nov 6, 10:37 am, mawei1981 <[EMAIL PROTECTED]> wrote:
>
> > Hi, All
>
> > As we know, the database provide a unique key not a primary key to
> > support we store some content we do
On Nov 6, 12:13 pm, Andy Freeman <[EMAIL PROTECTED]> wrote:
> Can't this be done with a carefully constructed key_name?
>
There's a couple differences.
Unique key means throw exception on duplication. Save duplicated
key_name will cause overwritten. You have to use get_or_insert to test
uniquenes
On Nov 6, 9:39 am, yejun <[EMAIL PROTECTED]> wrote:
> On Nov 6, 12:13 pm, Andy Freeman <[EMAIL PROTECTED]> wrote:
>
> > Can't this be done with a carefully constructed key_name?
>
> There's a couple differences.
> Unique key means throw exception on duplication. Save duplicated
> key_name will cau
thanks for the discussion, all! just fyi, i'm going to respond on the
issue:
http://code.google.com/p/googleappengine/issues/detail?id=178
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To
