Common-lisp -*-
;;
;; Copyright (C) 2011 TechNo Wait.
;; All rights reserved.
;;
;; Author: Alain Picard
;;
Code:
(in-package :elephant)
(defun *test-tree* ()
(or (get-from-root :test-tree)
(add-to-root :test-tree (make-btree
(defun ap/prepare-1 ()
(dotimes (i 10)
Ian Eslick writes:
> Association slots were added recently and have not been fully tested.
> They should be considered in beta.
>
> If I send you a short description in the next few days will you
> volunteer to update the docs? :)
Possibly, but I can't make promises. I might have a couple
Dear Pachyderm lovers,
I'm noticing that the manual describes "derived slot indices",
however I can find no tests or example usage of these.
Conversely, I can find a test for what appears to be a very
cool feature: ":associate" type slots (in testassociations.lisp)
but can find no mention of the
"Leslie P. Polzer"
writes:
> But STORE-CONTROLLER is not a persistent class, so that's neither
> needed nor possible.
Doh!! :-)
--
Please read about why Top Posting
is evil at: http://en.wikipedia.org/wiki/Top-posting
and http://www.dickalba.demon.co.uk/usenet/guide/faq_topp.html
Please read
"Leslie P. Polzer"
writes:
> FWIW I guess most projects wouldn't accept such a patch. It's
I understand that perfectly, which is why I was happy to provide
a new patch. No harm done. It's just that I've forced everone
on my team for 10 years to use the same .emacs file, so there's
never any "e
Alain Picard
writes:
OK - here is a MINIMAL patch. It applies with
patch -p1 < /tmp/patch.
Hope this one works!
--ap
diff -rN -wu old-elephant-1.0-work/src/elephant/controller.lisp new-elephant-1.0-work/src/elephant/controller.lisp
--- old-elephant-1.0-work/src/elephant/controller.l
"Leslie P. Polzer"
writes:
> Alain Picard wrote:
>
>>> You could also make a Darcs patch using "darcs record" followed by
>>> "darcs send -o mypatch", although in the general case I prefer plain
>>> diffs.
>>
>> OK - her
"Leslie P. Polzer"
writes:
> But this one doesn't apply cleanly here:
> You could also make a Darcs patch using "darcs record" followed by
> "darcs send -o mypatch", although in the general case I prefer plain
> diffs.
OK - here's a patch produced as above.
Sat Oct 17 10:28:34 EST 2009 dr.ala
"Leslie P. Polzer"
writes:
> I'd be happy to review and apply your patch. It should contain a test
> case if that's possible.
OK, here it is. Sorry, I don't have a test case, but I did verify
that it now works properly from two separate processes when I
now pass :register t to OPEN-STORE.
Thi
The current version of GET-CON is broken. The code reads:
(defmethod get-con ((instance persistent))
(let ((con (fast-lookup-con-spec (db-spec instance
(cond ((not con)
(aif (slow-lookup-con-spec (db-spec instance))
(progn
Ian Eslick writes:
> There was a bug with the get-con function that returns nil after the
> restart. I just checked in a fix for that and went ahead and
> implemented your suggestion for a saner error + restart model.
That's great. I'll do a checkout and start playing with that
tomorrow.
Ian Eslick writes:
> I can say more later, but given controller opening costs, we should
I will definitely be looking forward to your further exposition. :-)
But as...
> Sent from my iPhone
I can definitely understand why you'd want to be brief.
Cheers,
--ap
___
rts of errors might get
thrown and how I'm supposed to handle them during "normal" elephant work.
A section documenting the responsibilities of the programmer in this
area would be invaluable, IMHO.
Thanks for any pointers!
--Alain Picard
--
Please read about why To
"Leslie P. Polzer"
writes:
> Would you propose that Elephant check the type as well
> when serializing slots?
I'm a bit of two minds about it. I might be jaundiced in my
view because the systems I've used before was an O-R mapping
system, and there it made sense to assert in lisp---if you
didn'
itarg :name)
(position :type position
:accessor foo-position
:initform 1))
(:metaclass persistent-metaclass))
Elephant will happily let me store 100 in the foo-object position slot.
Cheers,
Alain Picard
--
Please read about wh
"Robert L. Read" <[EMAIL PROTECTED]> writes:
> The contract is that make-instance should only be called once for a
> given object?
FWIW, I wrote a CLOS->SQL layer a few years ago, and I do agreed
with this assessment (that MAKE-INSTANCE should only get called once),
so my protocol ended up with t
"Alex Mizrahi" <[EMAIL PROTECTED]> writes:
> AP> When I tried the above, it blew up when I added the
> ENSURE-TRANSACTION
> AP> clause; because all of a sudden the DOQUERY found itself querying
> AP> on the "wrong" database. (I'm assuming ENSURE-TRANSACTION binds
> AP> something like a *DATAB
nsidered these sorts of issues and if there is a
"recommended" way of proceeding in a case such as this. I guess
the first thing I'd try is to bind something way up in the elephant
call stack which would cause all lower level "raw" postmodern calls
to act on the same DB that t
Ian Eslick <[EMAIL PROTECTED]> writes:
> What prospects are there for having a reasonable map implementation in
> postmodern?
Surely the prospects must be good; it's not very different
from what Lispworks' CommonSQL does with MAP-QUERY.
> 4) btrees are lightweight in BDB, but heavy in SQL - sou
"Henrik Hjelte" <[EMAIL PROTECTED]> writes:
> We have recently discovered some performance (and possibly other)
> problems, you might even call them bugs, with both map-index and the
> current implementation of cursors in the postmodern backend. Alex
> Mizrahi will reimplement things in a new way
"Alex Mizrahi" <[EMAIL PROTECTED]> writes:
> AP> Am I missing something really basic here?
>
> actually it's quite strange situation that you have *many* employees
> with same name but you want just one (random one). i cannot imagine
> why one needs this in real world..
I didn't say they have th
rn
equivalent of CLSQL's START-SQL-RECORDING.
Thanks in advance!
Alain Picard
--
Please read about why Top Posting
is evil at: http://en.wikipedia.org/wiki/Top-posting
and http://www.dickalba.demon.co.uk/usenet/guide/faq_topp.html
Please read about why
Ian Eslick <[EMAIL PROTECTED]> writes:
> Now you can approximate this by mapping your non-integer objects into an
> integer space according to your own ordering. This is provided for in
> the (add-class-derived-index ...) ... [SNIP]
Ah, ok. I missed that. That's kinda what I had in mind by a p
Pierre THIERRY <[EMAIL PROTECTED]> writes:
> Scribit Alain Picard dies 17/11/2006 hora 21:18:
>> This little snippet fixes this problem:
>> (change from the 0.6 distribution)
>
> Could you just provide the patch, that would be more easy both to read
> and apply? (fo
isps, nor do I really know what forms are appropriate
in any other lisps.
Obviously, it is possible to extend this scheme to let users register
their own comparison functions for more complex types; I'll let you
judge if this is worth the effort.
Hoping this helps someone, somewhere.
If th
25 matches
Mail list logo
