Indeed. A key should be though of as a UUID/GUID rather then a SQL
key.
On Oct 11, 4:33 pm, "David Symonds" <[EMAIL PROTECTED]> wrote:
> On Sun, Oct 12, 2008 at 6:30 AM, Roy Leban <[EMAIL PROTECTED]> wrote:
>
> > On Aug 22, 9:55 am, "Marzia Niccolai" <[EMAIL PROTECTED]> wrote:
> >> You can't qu
On Sun, Oct 12, 2008 at 6:30 AM, Roy Leban <[EMAIL PROTECTED]> wrote:
>
> On Aug 22, 9:55 am, "Marzia Niccolai" <[EMAIL PROTECTED]> wrote:
>> You can't query for the key, there is really no need.
>
> I disagree that there is no need. I have some code that deals with a
> wide variety of models. Th
On Aug 22, 9:55 am, "Marzia Niccolai" <[EMAIL PROTECTED]> wrote:
> You can't query for the key, there is really no need.
I disagree that there is no need. I have some code that deals with a
wide variety of models. The name of the model is passed in, so I do
not have the model object. I want to d
Hi,
I'm not sure exactly your use case, so I'm just going to describe in general
what I might do in a similar situation.
Say I have a list of keys for a picture model, and I want to render that
picture on my HTML page. So, let's assume these are my models:
class FirstModel(db.Model)
my_pics =
Hi Mariza,
ive been having the same issue as ARMIX,
my question is i have a page model one of the page models propertys is
a field called pics which is a list property
im storing a list ok keys from a photo model ... the idea is page has
a number of photos.
from what your saying i think ill nee
