From elephant-devel at common-lisp.net Sat Feb 23 19:08:19 2008 From: elephant-devel at common-lisp.net (elephant) Date: Sat, 23 Feb 2008 19:08:19 -0000 Subject: [elephant-ticket] #77: Class level indexed class operations across multiple stores Message-ID: <082.9d31e25f8a29c69278ac9393ed2fe7a0@common-lisp.net> #77: Class level indexed class operations across multiple stores --------------------------+------------------------------------------------- Reporter: ieslick | Owner: ieslick Type: defect | Status: new Priority: minor | Milestone: Component: metaprotocol | Version: Keywords: | --------------------------+------------------------------------------------- The recent configurable multi-store-indexing allows us to have indexed classes dealt with on a per-store basis, but what if we want to index over all objects in all stores? This requires a merge operation on top of each store's get-instances-by-xxx. Not hard to do, but requires some work. -- Ticket URL: elephant elephant From elephant-devel at common-lisp.net Sat Feb 23 19:08:27 2008 From: elephant-devel at common-lisp.net (elephant) Date: Sat, 23 Feb 2008 19:08:27 -0000 Subject: [elephant-ticket] Re: #77: Class level indexed class operations across multiple stores In-Reply-To: <082.9d31e25f8a29c69278ac9393ed2fe7a0@common-lisp.net> References: <082.9d31e25f8a29c69278ac9393ed2fe7a0@common-lisp.net> Message-ID: <091.8412fcd20a66f47af86f9261d326f1f5@common-lisp.net> #77: Class level indexed class operations across multiple stores ---------------------------+------------------------------------------------ Reporter: ieslick | Owner: ieslick Type: enhancement | Status: new Priority: minor | Milestone: Component: metaprotocol | Version: Resolution: | Keywords: ---------------------------+------------------------------------------------ Changes (by ieslick): * type: defect => enhancement -- Ticket URL: elephant elephant From elephant-devel at common-lisp.net Wed Feb 27 19:36:09 2008 From: elephant-devel at common-lisp.net (elephant) Date: Wed, 27 Feb 2008 19:36:09 -0000 Subject: [elephant-ticket] #78: Persistent associations Message-ID: <082.71cf69a0b78e34dbe66bb457af08498a@common-lisp.net> #78: Persistent associations --------------------------+------------------------------------------------- Reporter: ieslick | Owner: ieslick Type: enhancement | Status: new Priority: major | Milestone: Component: metaprotocol | Version: Keywords: | --------------------------+------------------------------------------------- With psets and a bit of hackery, we can create slots that maintain a list of other objects and insert/remove objects from the pset. ManyToMany slots in SQL systems are maintained by doing a lookup in a separate table consisting of pairs of related elements. This table consists of a pair ID and the pair of UID references. Speeding accesses to these tables can be tricky (index on each pair value, for instance). This ticket proposes that, as part of the referential integrity fix in ticket #3, we extend slot semantics to support native associations. cl-perec has a more SQL oriented model of associations by defining them external to the class as functions rather than slot definitions. This probably makes sense. You declare an association and the methods used to access them from either object - virtual slots that use the new table to lookup the association. A class should be able to keep track of the associations defined against it for introspection purposes. This info will have to be stored in the database, so this feature might be co-resident with an explicit storage of schemas in the DB. Bootstrapping is also an issue. Code defines the mapping, but connection to the persistent storage may come after code definition time so, like class indexing, connection happens on the first access. For multi-store operations, associations will only exist between instances of classes in the same store. -- Ticket URL: elephant elephant From elephant-devel at common-lisp.net Thu Feb 28 02:22:44 2008 From: elephant-devel at common-lisp.net (elephant) Date: Thu, 28 Feb 2008 02:22:44 -0000 Subject: [elephant-ticket] Re: #5: Automated indexing outside instances of a single class In-Reply-To: <082.6e9e348bb82fb7dfaad055e6e2136003@common-lisp.net> References: <082.6e9e348bb82fb7dfaad055e6e2136003@common-lisp.net> Message-ID: <091.f1c5a697da8cf49254a286491dcc1bcf@common-lisp.net> #5: Automated indexing outside instances of a single class ---------------------------+------------------------------------------------ Reporter: ieslick | Owner: ieslick Type: enhancement | Status: new Priority: blocker | Milestone: Release 0.9.2 - Schemas and Advanced Indexing Component: metaprotocol | Version: Resolution: | Keywords: ---------------------------+------------------------------------------------ Comment (by ieslick): Let's introduce the idea of a persistent mixin! Since I think we're moving to a slot and not class oriented view of indexing, this may cover the case of cross-heirarchy slot indexing. It most likely has a performance cost that needs to be thought through. -- Ticket URL: elephant elephant From elephant-devel at common-lisp.net Thu Feb 28 21:24:04 2008 From: elephant-devel at common-lisp.net (elephant) Date: Thu, 28 Feb 2008 21:24:04 -0000 Subject: [elephant-ticket] Re: #78: Persistent associations In-Reply-To: <082.71cf69a0b78e34dbe66bb457af08498a@common-lisp.net> References: <082.71cf69a0b78e34dbe66bb457af08498a@common-lisp.net> Message-ID: <091.05131afd6a00f6a91b048c292055ff8b@common-lisp.net> #78: Persistent associations ---------------------------+------------------------------------------------ Reporter: ieslick | Owner: ieslick Type: enhancement | Status: assigned Priority: major | Milestone: Release 0.9.2 - Schemas and Advanced Indexing Component: metaprotocol | Version: Resolution: | Keywords: ---------------------------+------------------------------------------------ Changes (by ieslick): * milestone: => Release 0.9.2 - Schemas and Advanced Indexing * status: new => assigned -- Ticket URL: elephant elephant From elephant-devel at common-lisp.net Thu Feb 28 21:28:12 2008 From: elephant-devel at common-lisp.net (elephant) Date: Thu, 28 Feb 2008 21:28:12 -0000 Subject: [elephant-ticket] Re: #56: Make Elephant asdf-installable In-Reply-To: <082.e110765ce0de93869689605c9022548f@common-lisp.net> References: <082.e110765ce0de93869689605c9022548f@common-lisp.net> Message-ID: <091.1958c3761a01a366171a82f68075a484@common-lisp.net> #56: Make Elephant asdf-installable --------------------------+------------------------------------------------- Reporter: ieslick | Owner: ieslick Type: enhancement | Status: new Priority: minor | Milestone: Release 1.1 Component: system-wide | Version: Resolution: | Keywords: --------------------------+------------------------------------------------- Changes (by ieslick): * milestone: => Release 1.1 Comment: This doesn't make a ton of sense until we get a lisp-only datastore, prevalence or otherwise so that it can load and work after being downloaded. -- Ticket URL: elephant elephant