Or you can add your primary key to the ObjEntity. This isn't done by
default for you, since primary keys are usually database artifacts that
probably shouldn't be exposed or needed by the application. Of course,
that all depends on how your application was designed/etc, too. Some
existing schemas/applications have natural data as keys and need it
exposed (or just rely on the key for lookups, but that could cause
security issues).
/dev/mrg
-----Original Message-----
From: Mike Kienenberger [mailto:mkienen..mail.com]
Sent: Friday, September 16, 2005 2:10 PM
To: cayenne-deve..bjectstyle.org
Subject: Re: EOF import question
I'm a novice when it comes to predefined queries or queries generated
from strings, but I think there's a db: prefix you can use to force it
to use a Db attribute.
http://www.objectstyle.org/cayenne/userguide/expressions/common.html
On 9/16/05, John Martyniak <jmarty..x.netcom.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Ok so. I have imported a EO model, and I have a Query that uses the
> primary key as one of its parameters. However the primary key is
> only in the DBEntity and not in the ObjEntity. When I go to save it
> I get the following error:
>
> Warning: Invalid Path in qualifier: 'itemId'
>
> It seems to me that this should use both the DBentity and objentity
> as the source for these attributes.
>
> Am I looking at this from the wrong direction?
>
> - -John
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP Desktop 9.0.1 (Build 2185)
>
> iQEVAwUBQysIqaF6YHs+0wZ7AQgBVwf/esgFYcpu3RQnP/fb7W0UeH/kSOOmxSl4
> PLXwnRRydlzRTX0pwKaRfdpvU1CYoMyinfXzcySppUGbaogjIm+L6iYH+6QIaWg9
> ZoWEtUJew4gjrvk0SVP6uzHn9Sx2OHfhKlhzLyzxyQ8PWI0EOWX6k1k729FUm/eY
> EY0vjP1yOZgT5vIOHI47PYkXzKWr+xzoO1gDz3bGh2CzP/2j0WJxu7YAdUMBkaRa
> zw14q6yaHSvZhPMiNxMNEggy8PhQ0bkUJFpBC9LBjA9jomIhL/vOr6ZeP8y6sb8s
> y81I91lKLxvAa//fMl95GP8NybwW9So/U6O4n42G35DUZv+WSIPa8A==
> =MsBD
> -----END PGP SIGNATURE-----
>
This archive was generated by hypermail 2.0.0 : Fri Sep 16 2005 - 14:18:06 EDT