[elephant-devel] A thorny problem....

[Robert L. Read]

Holy smokes!  Good thing I had the good sense to stay out of the way...

On Sat, 2006-02-18 at 13:39 -0500, Ian Eslick wrote:

> With the separate backend system I'm implementing you can specify that
> only CLSQL backends can be loaded so you will be able to debug backends
> against lisps independently without much problem.
> 
> Robert, I'm mostly done with the conversion although I got carried away
> on scope a bit.  I'm testing it now and should be checking it in this
> afternoon.
> 
> Ian
> 
> Robert L. Read wrote:
> > Excellent!  It would be wonderful if it would work with lispworks.
> >
> > It is certainly reasonable to create a "lispworks+CLSQL" only
> > solution OR a "lispsworks+BDB" only solution; I would be happy
> > to roll that into a release, and hope that in the future the full feature
> > set would be supported.
> >
> >
> > On Sat, 2006-02-18 at 18:33 +0100, Klaus Harbo wrote:
> >> On 17/02/2006, at 16:17, Robert L. Read wrote:
> >>
> >> > I think I've a identified a serious problem relating to the
> >> > the dependencies on various modules that I offer up
> >> > for you comment.
> >> >
> >> > I major goal of the multiple backend system is to allow
> >> > you to not need to install the software related to the system
> >> > you don't need.  If you want to use BerkeleyDB, you shouldn't have
> >> > to install CL-SQL.  If you want to use CL-SQL and a relational  
> >> > database,
> >> > you can't shouldn't have to install BerkeleyDB (which would subject
> >> > you to their license, in any case.)
> >>
> >> I have spent some time looking at what it would take to make Elephant  
> >> work with Lispworks.  It would a considerable advantage if I could  
> >> deal with making one backend work at a time.
> >>
> >> -Klaus.
> >>
> >> PS I case you're wondering, the status of this effort is that I can  
> >> get basic values into and out from the Postgres backend store,  
> >> whereas I keep getting EAGAIN signals whenever I try to use the  
> >> Berkeley backend.  I haven't had time yet to look more into getting  
> >> persistent classes work.  The Berkeley backend required a significant  
> >> number of changes, since the code generated by UFFI for Lispworks  
> >> requires placeholder (dummy) arguments for :out parameters, where  
> >> Allegro and SBCL/CMUCL seem to want none. 
> >> _______________________________________________
> >> elephant-devel site list
> >> elephant-devel at common-lisp.net <mailto:elephant-devel at common-lisp.net>
> >> http://common-lisp.net/mailman/listinfo/elephant-devel
> >>     
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > elephant-devel site list
> > elephant-devel at common-lisp.net
> > http://common-lisp.net/mailman/listinfo/elephant-devel
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/elephant-devel/attachments/20060218/28e9b14f/attachment.html>