From elephant-devel at common-lisp.net Wed May 2 19:21:25 2007 From: elephant-devel at common-lisp.net (elephant) Date: Wed, 02 May 2007 19:21:25 -0000 Subject: [elephant-ticket] #58: Clearly document btree sorting guarantees Message-ID: <082.87896e2878f88ea84f3717f8ca687d79@common-lisp.net> #58: Clearly document btree sorting guarantees -------------------------+-------------------------------------------------- Reporter: ieslick | Owner: ieslick Type: task | Status: new Priority: minor | Milestone: Release 0.9.1 - Low Hanging Fruit Component: serializers | Version: Keywords: | -------------------------+-------------------------------------------------- -- Ticket URL: elephant elephant From elephant-devel at common-lisp.net Wed May 2 19:22:52 2007 From: elephant-devel at common-lisp.net (elephant) Date: Wed, 02 May 2007 19:22:52 -0000 Subject: [elephant-ticket] #59: Integrate the prevalence data store Message-ID: <082.eef6cc73f3412eb55c5568ce7df88f2f@common-lisp.net> #59: Integrate the prevalence data store -------------------------+-------------------------------------------------- Reporter: ieslick | Owner: ieslick Type: enhancement | Status: new Priority: major | Milestone: Release 0.9.8 - Integrate New Data Stores Component: system-wide | Version: Keywords: | -------------------------+-------------------------------------------------- -- Ticket URL: elephant elephant From elephant-devel at common-lisp.net Sat May 5 04:41:46 2007 From: elephant-devel at common-lisp.net (elephant) Date: Sat, 05 May 2007 04:41:46 -0000 Subject: [elephant-ticket] #60: Fix sorting in lisp-compare-xxx functions Message-ID: <082.b5e2d0fa396b71ab7181e59328de6095@common-lisp.net> #60: Fix sorting in lisp-compare-xxx functions -------------------------+-------------------------------------------------- Reporter: ieslick | Owner: ieslick Type: defect | Status: new Priority: critical | Milestone: Release 0.9.1 - Low Hanging Fruit Component: system-wide | Version: Keywords: | -------------------------+-------------------------------------------------- Our in-lisp sorting is less general than the one in Berkeley DB, and a little less general than the one in CLSQL. We should unify the prevalence, clsql and existing lisp comparison functions into a clean function that is API compatible with BDB. -- Ticket URL: elephant elephant From elephant-devel at common-lisp.net Sat May 5 23:46:40 2007 From: elephant-devel at common-lisp.net (elephant) Date: Sat, 05 May 2007 23:46:40 -0000 Subject: [elephant-ticket] #61: Clean up and validate examples Message-ID: <082.fb72a07e9af731613308ce1c39bfb95d@common-lisp.net> #61: Clean up and validate examples -------------------------+-------------------------------------------------- Reporter: ieslick | Owner: ieslick Type: defect | Status: new Priority: minor | Milestone: Release 0.9.5 - Cleanup Messy Code Component: system-wide | Version: Keywords: | -------------------------+-------------------------------------------------- The blog example is out of date. Include the hutchentoot example, etc. -- Ticket URL: elephant elephant From elephant-devel at common-lisp.net Mon May 7 20:27:00 2007 From: elephant-devel at common-lisp.net (elephant) Date: Mon, 07 May 2007 20:27:00 -0000 Subject: [elephant-ticket] #62: Transaction validation tests Message-ID: <082.abe3e7a33cd008b60a17e771a946946c@common-lisp.net> #62: Transaction validation tests -------------------------+-------------------------------------------------- Reporter: ieslick | Owner: ieslick Type: defect | Status: new Priority: critical | Milestone: Release 0.9.7 - Test Review Component: system-wide | Version: Keywords: | -------------------------+-------------------------------------------------- There are no ACID tests! We need to validate that an aborted transaction actually aborts, that concurrent transactions are isolated and that transactions are durable under a variety of conditions (crash, loss of store controller, etc). -- Ticket URL: elephant elephant From elephant-devel at common-lisp.net Tue May 8 01:44:48 2007 From: elephant-devel at common-lisp.net (elephant) Date: Tue, 08 May 2007 01:44:48 -0000 Subject: [elephant-ticket] #63: add :elephant to feature list Message-ID: <082.ac001ff528598c0436f95cb32989b5af@common-lisp.net> #63: add :elephant to feature list -------------------------+-------------------------------------------------- Reporter: mac chan | Owner: ieslick Type: defect | Status: new Priority: trivial | Milestone: Component: system-wide | Version: 0.9 Keywords: | -------------------------+-------------------------------------------------- We want to have this somewhere in the source code (pushnew :elephant *features*) (preferably we only execute this when the elephant is loaded without any errors, so maybe add this in a file at the end of the asdf dependency list) -- Ticket URL: elephant elephant From elephant-devel at common-lisp.net Fri May 11 15:30:51 2007 From: elephant-devel at common-lisp.net (elephant) Date: Fri, 11 May 2007 15:30:51 -0000 Subject: [elephant-ticket] #64: A modern test framework Message-ID: <082.0e358e1cbfe43d2bdeba8676a6a77e06@common-lisp.net> #64: A modern test framework -------------------------+-------------------------------------------------- Reporter: hhjelte | Owner: ieslick Type: enhancement | Status: new Priority: major | Milestone: Component: system-wide | Version: Keywords: | -------------------------+-------------------------------------------------- The rt test framework is in my humble opinion a pain to work with. Tests can seldom be run on their own, because they have dependencies between them. And they don't tell you that they do, so the test will look like it's failing but the reason is because another test updated some global state. Also rt:s style to return the test result as values which is compared to a list is difficult to read. I propose (and volunteer) to update the test framework to something modern and stylish like FiveAM that can do hierarchical tests. This will make it much easier to maintain and code elephant. http://aperiodic.net/phil/archives/Geekery/notes-on-lisp-testing- frameworks.html -- Ticket URL: elephant elephant From elephant-devel at common-lisp.net Wed May 30 03:18:59 2007 From: elephant-devel at common-lisp.net (elephant) Date: Wed, 30 May 2007 03:18:59 -0000 Subject: [elephant-ticket] #65: Proper interface for informative messages and event logging Message-ID: <082.2ec8fa17e4cf6be51f297d4581e4e8fe@common-lisp.net> #65: Proper interface for informative messages and event logging -------------------------+-------------------------------------------------- Reporter: ieslick | Owner: ieslick Type: enhancement | Status: new Priority: trivial | Milestone: Component: system-wide | Version: Keywords: | -------------------------+-------------------------------------------------- Currently we print, signal or do other things when various system events occur. We should turn this into an appropriate log-level notification system where the user can specify the informativeness they want. Warnings and above should be printed by default to help the user avoid shooting themselves in the foot. Do we want to also add basic event logging such as: High level: (created pobj of : oid = foo) (created new repository ) Low level: (wrote , to ) (deleted from ) (slot-access to => ) This could be done easily as around or after methods on the major interfaces, perhaps enabled as a reader option (rather ugly, but performance enhancing). We could also just insert code into the appropriate places. -- Ticket URL: elephant elephant