?
or it is applicable in the Pilog context? how would one go about using
composite primary keys?
thank you.
/e
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de
A litte bit of extra documentation in addition to the reference:
http://www.prodevtips.com/2008/10/09/pilog-solve-and-the-aux-relation/
On Wed, Mar 16, 2011 at 2:54 PM, Alexander Burger a...@software-lab.de wrote:
Hi Edwin,
anyone encountered creating a composite primary key for Pilog?
You
Hi Alex,
On Wed, Mar 16, 2011 at 3:54 PM, Alexander Burger a...@software-lab.de wrote:
Hi Edwin,
anyone encountered creating a composite primary key for Pilog?
You mean for database indexes?
not just for indexes but for a composite primary key. i'm not sure tho
if my head is right on this.
Hi Edwin,
checking the docs out, +Aux is a Prefix class maintaining auxiliary
keys for +relations, in addition to +Ref or +Idx indexes. Expects a
list of auxiliary attributes of the same object, and combines all keys
in that order into a single index key.
which means that there must exist
Hi Edwin,
You mean for database indexes?
not just for indexes but for a composite primary key. i'm not sure tho
if my head is right on this.
Yes. I'm using key and index for the same thing, I think.
In my mind, I distinguish between objects and indexes in the DB. The
objects are the
Hi Alex,
On Wed, Mar 16, 2011 at 4:44 PM, Alexander Burger a...@software-lab.de wrote:
In my mind, I distinguish between objects and indexes in the DB. The
objects are the payload data, and also have direct links between each
other (the +Link and +Joint relations).
uhm. this helps a lot.
