On Fri, 2008-10-24 at 09:11 +0200, Leslie P. Polzer wrote:
> The only major problem with it is that the Postmodern backend
> hasn't kept up with the schema evolution changes.
I did a bunch of work back in the spring to bring postmodern up-to-date,
and there were just a few failing tests at that t
Actually, I think it is necessary to have such conversations, and they
are bound to sound more heated in email than they would over coffee; but
we are a distributed team, and have to spend time in such communication
costs.
The most important thing is that this little community is making
progress,
I tend to agree with Alex. I don't think we need to optimize our use of
source control. I know nothing about Mercurial, having used only CVS,
subversion, and Darcs but I think getting 1.0 done should be our focus.
On Wed, 2008-10-22 at 21:58 +0300, Alex Mizrahi wrote:
> LPP> At least one
Yes, I'm happy to write something.
On Tue, 2008-10-21 at 23:12 -0400, Ian Eslick wrote:
> If no one has answered this, I'd suggest the website as a canonical
> reference. I don't think there are any actual pubs, although I'm
> minded to write a paper for the '09 lisp conference at MIT. (Any
I think it largely that no one tests on that platform.
However, I personally don't know what the state of readiness of any lisp
on Windows is. Elephant itself is moderate in its use of outside
systems, such as CL-SQL and BDB.
Someone who already had some experience porting to a Windows platform
Dear Leslie,
I have applied your two most recent patches to elephant-unstable; they
seemed to pass the tests under BDB for me as well. Thanks for your
contribution; let me know if I didn't get it quiet right.
On Tue, 2008-09-09 at 21:35 +0200, Leslie P. Polzer wrote:
> Darcs patch attach
The Elephant-unstable branch is currently broken for all non-bdb builds.
I suspect this is some confusion in the way things have been checked in.
I am trying to reconstruct what happened. I find it a lot harder to
figure things like this out in darcs than in subversion or cvs.
In all probabilit
On Fri, 2008-06-13 at 17:36 -0500, Sebastian Georges wrote:
> Nobody?
You may have to ask more explicit questions than this to get help.
As I mentioned, I can't reproduce the problem, although it seems to
work on sqlite3 for me.
Can you do something to generate a stack trace, and post that?
Obviously, I am biased, not by self-conceit but by familiarity with DCM.
I think something like DCM, in which you use a write-through in-memory
cache, is very workable. To my mind, an ideal system would allow cache
policy to be set separately from the concurrency control and elephant
usage. To m
If one could operate under the assumption that most of the database fits
into memory, I would say the act of dealing with references that would
be left dangling is definitely better handled at the "business object"
layer. This would mean that in the "delete" method for each class, it
would know wh
s /temp/blog.db already exist? Is it possible that this is a problem
in an "upgrade" from a previous format?
On Mon, 2008-06-09 at 21:35 -0500, Robert L. Read wrote:
> I'll try this and report back. I haven't tested with sqlite3 since I
> switched to a 64-bit comput
I'll try this and report back. I haven't tested with sqlite3 since I
switched to a 64-bit computer.
On Mon, 2008-06-09 at 17:03 -0500, Sebastian Georges wrote:
> I tried to install elephant-unstable this morning (as drop-instance
> and some keyword arguments are not available in 0.9.1 i guess
Great! This is the almost the last piece we need before the upcoming
release.
On Mon, 2008-05-26 at 10:55 +0300, Alex Mizrahi wrote:
> i've implemented stuff required to make it fly this weekend
> (due to lack of internet connectivity), but apparently i've messed
> something:
>
> Did 407 chec
Dear Glenn,
I have applied your patch to elephant-unstable. Thank you.
Unfortunately, I can not build the documentation right now due to an
error in compiling defpackage in sb-posix, therefore I cannot verify
that that works. What version of SBCL are you using (I'm on 1.0.13).
Ar
That is the correct way to do it, thank you.
I will apply the patch today or tomorrow.
On Sun, 2008-05-18 at 17:37 -0400, Glenn Tarcea wrote:
> Hi,
>
> I've started trying to make some changes to the documentation. I've
> run into a couple of problems. Attached is a patch to
> docstrings.l
On Fri, 2008-05-16 at 23:22 -0400, Ian Eslick wrote:
> Robert said:
>
> > I'll go out on a limb and say that offering object-level caching is
> > the single biggest performance enhancement we make for the most
> common
> > cases.
>
> A clarifying question. How did you ensure ACID properties
On Fri, 2008-05-16 at 11:26 -0400, Ian Eslick wrote:
> Prevalence is much, much faster because you don't have to flush data
> structures on each commit, so cl-prevalence performance with
> Elephant's data and transaction abstractions would be a really nice
> design point. I wonder if we woul
On Thu, 2008-05-15 at 10:39 +0300, Alex Mizrahi wrote:
> RLR> The purpose of compression is of course NOT to make the store smaller.
> RLR> It is to decrease the amount of I/O that is required to access the
> RLR> store.
>
> time to do I/O does not linearly depend on I/O amount.
>
> for exampl
On Wed, 2008-05-14 at 23:27 -0400, Ian Eslick wrote:
> Actually I wouldn't do that quite yet. If we're going to be putting
> things into the C world via BDB, then we should keep the serializer
> that is efficient at doing that!
>
Well, if we're willing to have type-specific serializers, I do
On Tue, 2008-05-13 at 23:36 +0200, Ryszard Szopa wrote:
> On Tue, May 13, 2008 at 4:01 PM, Ian Eslick <[EMAIL PROTECTED]> wrote:
> > I had just run into this myself too! Anyway, I made some tweaks to the
> > patch and just pushed the fix.
> >
> > You could write a whitebox test for the auxiliary
On Tue, 2008-05-13 at 10:17 -0400, Ian Eslick wrote:
> Robert or Alex, would you mind back patching on the main branch?
I have now applied Richards patch to the main branch -- thanks!
(I didn't run the tests, which is a bit naughty, but time is short.)
>
> We should deprecate the main branch an
I feel compelled to respectfully disagree with Alex's views stated
below.
The purpose of compression is of course NOT to make the store smaller.
It is to decrease the amount of I/O that is required to access the
store. I think this is where most of the time is spent. I suspect Alex
is correct th
On Wed, 2008-05-14 at 09:40 -0400, Ian Eslick wrote:
> If the BTree node binary data is stored in a lisp octet array, and
> we
> don't want to deserialize to compare keys, then we need to write the
> procedure that you can find in libberkeley-db.c in the src/db-bdb
> file. It performs a cont
I am certainly in favor of using fixed-size pages as a basic model. I
think this is very common. It has the advantage of allowing page-based
caching more easily. One can even contemplate things like a RAID-style
striping across machines on a LAN or WAN.
I think we should create a really pure-li
Dear Bryan and Team,
I have now removed the explicit load of cl-sql (I think) and put an
sbcl pragma around an explicit depend in both the "elephant" darcs
branch and the "elephant-unstable" darcs branch.
I observe the following comments in the CLBUILD wnpp-projects file,
w
On Tue, 2008-05-13 at 22:33 -0400, Glenn Tarcea wrote:
> BTW: If its alright I'm going to update the docs to add a section on
> having two versions of Elephant installed and using ASDF to manage
> them.
Please do.
___
elephant-devel site list
elephant-d
About two years ago I tried to use Montezuma and found it very buggy.
It may have gotten better. I had better luck using
"lucene-webeservice":
http://lucene-ws.net/
Which is (obviously) a webservice interface to a normal Lucene
installation. This worked pretty well for me. I used Closure-XML
t
On Mon, 2008-05-12 at 10:55 +0300, Alex Mizrahi wrote:
> GT> What do you all think about allowing two different versions of
> GT> Elephant to be installed at the same time?
>
> that's pretty easy.
>
> let's suppose that "stable" elephant is somewhere on your
> asdf:*central-registry* path.
>
ply")
> > (:file "request")
> > (:file "session")
> > (:file "misc")
> > (:file "easy-handlers")
> > (:file "headers")
> > #+(a
On Sun, 2008-05-11 at 14:22 -0700, Bryan Emrys wrote:
> At one point the clbuild maintainers looked at elephant but had some problems
> that prevented inclusion.
>
> Specifically:
>
> # - needs sb-posix, but doesn't declare that dependency, meaning that
> #it doesn't build even with a confi
On Sun, 2008-05-11 at 19:50 -0400, Glenn Tarcea wrote:
> What do you all think about allowing two different versions of
> Elephant to be installed at the same time? I tried to have both my
> original version of Elephant installed and also to install elephant-
> unstable. Currently there are a
OK, I have applied this patch.
I didn't run the tests. Ordinarily I do before accepting a patch, but
I assume if this causes a problem we will catch it quickly in our
current state.
Of course, please make sure you are all green before submitting a patch.
On Mon, 2008-05-05 at 14:07 +0200, Les
I have now committed an all-green solution for the CL-SQL backend to
elephant-unstable.
I don't know that it will help the Postmodern work much --- perhaps just
as a pointer for what needs to be done.
Nonetheless, it is ready for someone who wants to work on making
Postmodern work with elephant-u
On Sun, 2008-05-04 at 10:37 +0300, Alex Mizrahi wrote:
> RLR> implementing a new kind of btree that supports duplicates (hard).
>
> ain't btree with duplicates very similar to btree-index thing, because
> btree-index also supports duplicates?
Yes, I thought that too -- my initial strategy was t
Dear Team,
At the moment, as Ian has mentioned, the next major release is
dependent on the porting of a big chunk of new functionality that he has
written to the CL-SQL and Postmodern backends. I think it is worth a
status report on that.
I have spent a total of 24 hours of work
Thank you, Leslie.
It will take me a while to review this; I am working on
"elephant-unstable" right now.
On Thu, 2008-04-17 at 14:39 +0200, Leslie P. Polzer wrote:
> It seems I forgot to record the changes to variable.lisp.
> Amended patch attach.
>
> Leslie
> __
On Wed, 2008-04-16 at 02:37 +0200, Ryszard Szopa wrote:
> Hi,
>
> I've started using Elephant and I must say I am really surprised how
> easy and nice to use it is. However, there are some areas where I feel
> a bit lost, and I couldn't find the answers in the manual. I am using
> Elephant 0.9.1 w
On Mon, 2008-04-14 at 22:56 -0400, Glenn Tarcea wrote:
>
> >
> > You got the latest version from darcs, not CVS, correct? The darcs
> > repository is about six months ahead of the CVS repository.
> >>
>
> Ugh... Ok, I'll go to darcs and get the latest. I went to CVS. Are
> you sure still want
On Mon, 2008-04-14 at 21:03 -0400, Glenn Tarcea wrote:
> Ok, I guess it doesn't hurt to check out the CVS repository before
> asking questions. I downloaded the latest version of pset.lisp from
> CVS, and (at least for the moment) it seems to be working.
You got the latest version from darcs,
On Mon, 2008-04-14 at 21:03 -0400, Glenn Tarcea wrote:
> Ok, I guess it doesn't hurt to check out the CVS repository before
> asking questions. I downloaded the latest version of pset.lisp from
> CVS, and (at least for the moment) it seems to be working.
>
> Oh well, I guess this is a chance t
Thank you, Alex, that is a very nice solution. I have committed it to
the main repo.
Yes, I thought it did work in at least one place.
On Thu, 2008-04-10 at 10:51 +0300, Alex Mizrahi wrote:
> RLR> However, fixing those tests (or the concurrency problem they
> RLR> represent) under SBCL is a
-priority for me right now is making Ian's
recent changes work for the CL-SQL backend in the elephant-unstable
branch, so I cannot undertake this right now.
On Wed, 2008-04-09 at 08:10 +, Sean Ross wrote:
> On 4/9/08, Robert L. Read <[EMAIL PROTECTED]> wrote:
> > Thanks f
On Wed, 2008-04-09 at 13:36 -0400, Aaron Feng wrote:
> I have learned a good deal about elephant so far, but I'm still unsure
> on how to design my schema with elephant, so I'll post what I have
> later on today. All suggestions are welcome!
This may seem silly and you may be beyond it, but the
On Wed, 2008-04-09 at 00:06 -0400, Aaron Feng wrote:
> Robert,
>
> > I don't understand why you would explicitly call remove-kv.
>
> I'm trying to remove an item from a btree. Is there other function I
> can call instead of remove-kv? I'm indeed using persistent classes.
> I'll post my code la
On Tue, 2008-04-08 at 16:13 +0100, Sean Ross wrote:
> On 4/7/08, Jens Teich <[EMAIL PROTECTED]> wrote:
> > Lispworks 5.1
> > Mac OS X 10.5
> > ** Error in (DEFCLASS ELEPHANT:BTREE-INDEX):
> > Invalid allocation type INSTANCE for slot-definition-allocation
>
> There seems to have been a MOP c
On Tue, 2008-04-08 at 23:17 +0300, Alex Mizrahi wrote:
> > Will garbage collector be added into elephant in the future?
>
> I think so, I remember Ian Eslick mentioned it, but I don't know it it will
> be *near* future -- it is quite challenging thing.
> perhaps Ian will clarify if he has ideas
OK, I have committed this change, along iwth Leslie Polzer's two
patches, to the official repository.
Thank you, gentlemen.
On Mon, 2008-04-07 at 06:56 +0200, Jens Teich wrote:
> Hi,
>
> in CREDITS, you write:
>
> | Edi Weisz for Lispwork and Win32 patches
> |
> | Mac Chan for his Hutchentoot
On Mon, 2008-04-07 at 16:51 -0700, Vagif Verdi wrote:
> If I will make item class persistent, then items will be saved independently
> of their parent. That means manual housekeeping.
> When order object is deleted, I will have to intercept that and manually
> delete all items objects.
> And this i
I have applied this patch locally, and will apply it to the repository
along with Leslie Polzers, when I have reviewed them and tested them.
I think the Huchentoot reference is many years old; it may have been
germane at one time but lost its relevance.
On Mon, 2008-04-07 at 06:56 +0200, Jens Te
On Sat, 2008-04-05 at 12:51 +0300, Alex Mizrahi wrote:
> in elephant we have several different backends:
> * BDB one is primary one, APIs were modelled according to
> capabilities of
> BDB
> * CLSQL can work with any SQL database supported by CLSQL (that's
> good),
> but has some significant "s
On Thu, 2008-04-03 at 12:52 +0200, Leslie P. Polzer wrote:
> Hi guys,
>
> there are two tiny patches I've sent that must've been overlooked.
> One reverted a small previous change in the tutorial and one
> put the concurrency tests in a separate suite.
>
> Especially the latter one is important,
On Wed, 2008-03-26 at 20:33 +0100, Leslie P. Polzer wrote:
> I suppose this is a good opportunity for me to chime in with
> a few thoughts. Aren't B+trees a choice that is too conservative
> for a modern storage backend?
> There seem to be more modern data structures (S(b) trees or
> fractal trees)
Congratulations Ian!
Thanks for all the hard work.
I will help by working on this task:
On Sun, 2008-03-23 at 10:52 -0400, Ian Eslick wrote:
> - Upgrade Postmodern and CLSQL data stores - Support btrees with
> duplicate keys - Some minor API additions for upgrade &
> bootstrapping
That i
I think it is great that you two have reached a consensus. If Alex can
spend the time improving the tests that Leslie started along the lines
that he mentioned, I think that would be good progress for Elephant.
Thanks, gentlemen...each of these improvements makes Elephant a little
more robust.
On Mon, 2008-03-17 at 13:24 -0400, Ian Eslick wrote:
> I noticed this too but haven't had a chance to track it down. I don't
> see it on my local branch so I can check which patches went into head
> that aren't in unstable. I should probably do an import and integrate
> once I get my branch
On Mon, 2008-03-17 at 17:21 +0100, Leslie P. Polzer wrote:
> Hi Robert,
>
> > Furthermore, in attempt to solve this problem, I restored my local copy
> > to the head of the main repository, and am green only under BDB.
>
> I checked out a pristine copy and tried the BDB and PG tests, which al
Dear Alex,
Thank you very much for taking the time to deal with this. I
personally don't have much of an opinion about how it should be
done---except that it sure seems like a good idea to make it
configurable, which ought to keep everybody happy, and prevents me
having to make a decision
CLSQL - map-index-remove failed
> Mac OS X / SBCL / BDB 4.5 - no probs
> Mac OS X / SBCL / CLSQL - no probs
>
> (I don't have a postgres test db setup at the moment)
>
> Ian
>
> On Mar 16, 2008, at 3:15 PM, Robert L. Read wrote:
>
> > Dear Leslie and Ia
Dear Leslie and Ian Alex and Henrik,
I can see now that I did not apply Leslie's updated patch. I attempted
to rollback and reapply the correct patch. Unfortunately, I was unable
to get to a "green" state under any system. I find darcs much harder to
work with than CVS (however, I had a
On Tue, 2008-03-11 at 14:41 -0400, [EMAIL PROTECTED] wrote:
> Hi Ian,
>
> Thanks. I just downloaded the latest darcs and will look at it. I've
> been evaluating different querying to propose a syntax.
>
> BTW, in the darcs I downloaded 10 minutes ago, I ran the tests and got:
>
> Did 421 che
Dear Leslie,
Thanks for this patch. I have applied it to the main repository. I
hope you can work with Alex in the future to avoid any confusion, but in
any case I greatly appreciate the time you put into this.
I did personally have some problems...perhaps because Bordeaux Thread
On Thu, 2008-03-06 at 10:10 -0500, Ian Eslick wrote:
> I agree with Robert. The best way to start is to use lisp as a
> query
> language and essential do a search/match over the object graph.
>
> The rub comes when you start looking at performance. A linear scan
> of
I neglected to mention
Thanks! Rock on!
I will test them this weekend.
On Thu, 2008-03-06 at 14:16 +0100, Leslie P. Polzer wrote:
> Hello everyone,
>
> I wrote two concurreny test cases, added Bordeaux Threads and revised
> the Postmodern error and transaction handling (for example, deadlocks
> are no longer a proble
On Wed, 2008-03-05 at 21:50 -0800, Paul Legato wrote:
> I think the thing is not that we need professional consulting, but we
> are trying to become the professional consultants. :) Could you more
> knowledgable ODBMS coders recommend some good books or papers on the
> topic of ODBMS care and feedi
On Tue, 2008-03-04 at 22:38 -0500, Ian Eslick wrote:
> = Schema evolution and synchronization (Robert?)
>Most of the hooks are here, but tying up all the loose ends will
> take some sustained concentration
I'll try to help with this. Next week is our spring break and my family
is vacationi
On Tue, 2008-03-04 at 17:18 -0500, Ian Eslick wrote:
> My fellow Elephants,
>
> I've recently added support for a full schema evolution infrastructure
> on my local development branch. Every persistent class now has a
> schema object associated with it and each store that has one or more
>
On Mon, 2008-03-03 at 09:59 -0500, Ian Eslick wrote:
> It might make sense to just have it be a separate common-lisp.net
> project. We can have an optional elephant module that adds the
> appropriate dependencies and wraps it into the Elephant framework.
> (Perhaps a contrib for now until t
On Thu, 2008-02-28 at 16:32 +0100, Leslie P. Polzer wrote:
> > I'm imagining something that spins up 100 simultaneous threads and does
> > something to elephant from within each thread. Following the mantra
> > "red, green, refactor", it would be lovely to see things seize up and
> > then see
On Thu, 2008-02-28 at 09:45 +0100, Leslie P. Polzer wrote:
> Dear Robert,
>
> you must really be a fan of TDD :)
Yes. I have had the pleasure of pair programming with Kent Beck
himself.
But more to the point, the test suite in Elephant is one of our
strongest assets. Where it is weak (like in
Dear Leslie,
Thank you for this patch. I will try to test it by this weekend,
unless Ian wants to.
However, if you will forgive me being dogmatic, it would be even better
if this had a test case with it. For example, I don't think we have any
good examples of producing lots of th
Dear Team,
On Dec. 30th, Anton Kazennikov submitted the attached patch to make
Elephant work with BDB 4.6. (THANKS!) I twiddled my thumbs about it,
in part because I didn't know how many people were ready for 4.6.
It now seems that the time is ripe to make the move from 4.5 to 4
On Mon, 2008-02-25 at 15:14 +0100, Leslie P. Polzer wrote:
> Same for line 171. I wonder what's wrong?
>
I don't know why the patch didn't hash, but I was simply mistaken in not
seeing that 171 is the same; I must have gone to the wrong line number
or something. I apologize for the confusion.
I
Dear Leslie,
In attempting to apply the second of your three patches
(unicode2.patch), darcs says:
[EMAIL PROTECTED] elephant]$ darcs apply ../unicode2.patch
darcs failed: Patch bundle failed hash!
This probably means that the patch has been corrupted by a mailer.
The most likely culpri
Thanks!
I'm about to leave town, but should be able to review and commit this by
next Wednesday.
On Fri, 2008-02-22 at 10:13 +0100, Leslie P. Polzer wrote:
> > However, I wonder if it possible for you to turn whatever made you
> > notice it into a test-case? It is possible that this bug exis
Should you be using the darcs system? The CVS tree is about 6 months
out of date. I think you should either use one of the release tarballs
or use darcs to get the latest version.
On Thu, 2008-02-21 at 11:15 -0500, Ian Eslick wrote:
> >
> > I erased the entire elephant directory and re-downloade
No, I can't test this, because I don't have BDB installed on my x86_64.
On Thu, 2008-02-21 at 11:15 -0500, Ian Eslick wrote:
> Robert,
>
> Can you see if you can reproduce this. I can't get back to it now for
> a couple of days.
>
> Waldo, if you don't hear anything from us in a few days jus
Dear Leslie,
Thanks for this patch.
However, I wonder if it possible for you to turn whatever made you
notice it into a test-case? It is possible that this bug exists on the
LISP you are using and not mine, but in any case we should use each such
bug as an opportunity to expand th
I was green with this patch, although I am using PostGres 8.1, I think.
I have committed it to the official repository.
On Sat, 2008-02-16 at 11:22 +0200, Alex Mizrahi wrote:
> EN> I apologize if I've overlooked something obvious, but is the current
> EN> darcs Elephant with the current darcs Po
OK, I think I have applied those patches correctly.
Perhaps you could do a "darcs pull" or a "darcs diff" against the repo
to make sure I did it correctly; I still find darcs a little confusing,
and my private repo was not in sync with the offical one.
However, I was green with your changes in my
On Fri, 2008-02-15 at 10:29 +0100, Henrik Hjelte wrote:
> On Fri, Feb 15, 2008 at 9:10 AM, Alex Mizrahi <[EMAIL PROTECTED]> wrote:
> > i think it doesn't have sence to apply them now, though -- Henrik already
> > has updated patches that work better (that famous instances
> > reinitialization
>
On Thu, 2008-02-14 at 22:34 -0500, John DeSoi wrote:
> SQLite seems like it would be the ideal database for this project
> since it is easy to embed in an application and has no license
> hassles. I don't really know anything about BDB, but I'm surprised
> the
> performance of a properly inde
are astronomical, so decided to switch
> loyalty to LW. Let us see how this goes.
>
> For a product that cannot cost more than $500, and might not sell in huge
> numbers, this seems like too much trouble!
>
> Thanks for your advice.
> Regards,
> Rangarajan
> - Origi
On Wed, 2008-02-13 at 10:41 -0500, Ian Eslick wrote:
> The answer to all of this, I think, is having a native lisp version
> that has BDB's performance and no licensing restrictions. Then
> supporting the other two becomes: Postmodern for a higher degree of
> reliability as well as for distr
I am not a lawyer either, but I believe there is some confusion. You
correctly give a link to the most recent versions of BDB, which is
released by Oracle under quite different conditions than the original
sleepycat license.
By my reading of this license,
http://www.oracle.com/technology/softwar
th schema evolution when you change the design of your object
space. I think Elephant is much more convenient, but using CL-SQL
directly is an option.)
>
> Coming to your suggestion that it would be wise to build a very simple,
> native lisp backend without the "frills&quo
On Wed, 2008-02-13 at 16:06 -0500, Ian Eslick wrote:
> Re: Tokyo Cabinet
>
> The API is nearly identical to BDB's. I think a TC version of the
> datastore would be pretty easy to do. The only way it makes sense
> to
> me to do this is to deprecate the BDB data store as of the next
> major
I have applied this diff, thank you.
It appears from the post that you are computing it against an "old" and
new" repository, presumably local copies that you have made. This
prevents me from being able to apply the patches directly.
Although there may be circumstances in which you need to do th
I have applied this patch.
Next time, if you could uses the "darcs" diffing system rather than cvs,
it would tend to make things a little easier.
On Fri, 2008-02-01 at 11:51 +0100, Leslie P. Polzer wrote:
> > Patch attached.
>
> Alright, so I lied here. But it's attached with this one.
>
> Le
Thank you. I will apply it by Monday.
On Fri, 2008-02-01 at 11:51 +0100, Leslie P. Polzer wrote:
> > Patch attached.
>
> Alright, so I lied here. But it's attached with this one.
>
> Leslie
> ___
> elephant-devel site list
> elephant-devel@common-l
I am not entirely sure how to prevent this in the future.
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
Thank you. I was green under postmodern and cl-sql on postgres under
SBCL, so I have added your patches to the repo.
Thanks again.
On Mon, 2008-01-14 at 13:50 +, Sean Ross wrote:
> On Jan 11, 2008 4:34 PM, Sean Ross <[EMAIL PROTECTED]> wrote:
> > > I appreciate you providing this patch. Ho
Thank you Sean.
I don't feel I have enough experience to really comment on this idea, so
I will assume that it is a good one.
I appreciate you providing this patch. However, it would be even better
if this patch were accompanied with tests, or modifications to the
existing test suite, which exer
Thank you. I have fixed this in the repository.
On Fri, 2008-01-11 at 08:24 +0100, Norman Werner wrote:
> Hello,
>
> During trying out elephant for the first time I found a small typo in the
> documentation regarding the example code to use a cl-sql backend
> (http://common-lisp.net/project/
On Wed, 2008-01-09 at 11:02 +0200, Alex Mizrahi wrote:
> is my English that poor so nobody understand me??).
>
No, your English is great. I think there were so many emails yesterday
that it was hard to know exactly whom to respond to.
Thanks, this is great work; I'm sorry I couldn't figure it o
Thank you. I have committed this patch to the repository.
However, under sbcl on a x86_64 architecture, I have to build libmemutil
by hand, because of the errors below. I have no way to explain these.
After executing gcc by hand, it is not a problem.
This is the REPL error:
Implicitly c
Thank you, Anton.
I'm sorry it has taken so long to get to this (the holidays clog things
up.)
I applied this patch and was green under SBCL on postmodern and
postgres. I can't test under BDB, but I assumed this was enough
evidence to commit it to the repository, so I have done so.
If anybody
Thank you very much, Sean. I suggest you work with Henrik and Alex and
I on this as well (possibly off-line, outside of this forum.)
In case it helps, here is what I tried to do, and what I think I
discovered. Please forgive me if I am inconsistent; I clearly have been
confused on some of these
On Tue, 2008-01-08 at 10:31 -0500, Ian Eslick wrote:
> Actually I think we definitely need to fix this. Quite a few people
> have run into the problem that we're violating the CLOS contract on
> make-instance and that we should not use the same CLOS calling path
> for re-initialization that
Until we can resolve the issues Ian described, or at least make it work
with ele-postmodern.
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
I agree completely with Ian.
In fact I have now spent a very embarrassing 5 days trying to modify the
ele-postmodern interface to use "recreate-instance" based on Sean's
patches, and have failed miserably. This is the first time in my career
this has ever happened to me.
I wasted this time in pa
1 - 100 of 230 matches
Mail list logo
