Here is clsql-fluid with changes submitted, hope nothing is missed, works 
for me 
https://github.com/html/clsql-fluid

четверг, 5 апреля 2012 г., 2:12:47 UTC+3 пользователь Metacraft написал:
>
> I need to know the current status of weblocks + clsql status as of 
> March/April 2012 with respect to fluid/multi-threading? 
>
> I can partially run weblocks-clsql-demo only by removing the fluid 
> reference and direct clsql connect (although I do run into internal 
> error when adding employees or companies on the web demo). With the 
> original source (clsql+fluid) I get defmethod missing error on 
> database-type(clsql-sys:conn-pool). Direct CLSQL works (can create 
> database tables etc). 
>
> I have read about all of the dozens of the forum articles and page 
> that I could search on this topic. But there is no clear conclusion 
> (the discussion about clsql vs fluid regarding thread safety is one or 
> two years old). Then there are recommendations from CLSQL site about 
> not using fluid. Is there a version of weblocks mysql store that is 
> thread-safe and works (with or without fluid)? 
>
> I have tried weblocks-clsql-demo both on MacOS and on linux centos 5 
> using quicklisp downloads (that installed 
>  weblocks-20120305-git  clsql-20120305-git and clsql-fluid-20110730- 
> darcs - at least that is the name of its installed directories). 
> Running SBCL 1.0.51 compiled with threading enabled. 
>
> I really want to use weblocks for a production site, but need to use a 
> legacy mysql database. Any comments or suggestions will be greatly 
> appreciated. Is there any unfinished or TO-DO work in this area that 
> volunteers can help? 
>
>
> Thanks, 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weblocks" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/weblocks/-/EZErxX3df_8J.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/weblocks?hl=en.

Reply via email to