On Sun, Jan 2, 2011 at 18:00, Brit Butler <[email protected]> wrote: > Slobodan, > > Hi. Postmodern has been merged in as an "official" store though it's > not quite ready for production use to be honest. You would need to > manually manage per-request-thread database connections. This also > concerns the clsql backend to some degree (see the recent CLSQL-Fluid > thread).
Hm, well, thread management is next in line for me to learn and apply in the common lisp environment, one more reason to learn and understand it well. :) > I'm relieved to hear that you like it and that it's > simplifying *anything* at the moment. :) It is. I can use weblocks views in "the way they're meant to be used" :-) and it works quite nice. Also, I have been wandering for a while now what this store and persistence stuff was all about, and why I should use it. Now I understand, and it's great. > I'm going to finally settle in today and tomorrow to work on getting > the Store API extended for that. > > You raise a very good point about dao-table-name. That hadn't occurred > to me during development. Postgres definitely supports composite keys > so I'm not sure what your concern is with class-id-slot-name. Even if > "under the covers" it was actually only using one primary key, I don't > see the benefit in taking the car of the list. It would at best > *slightly* simplify some client code. Correct me if I'm wrong. Well, for some reason, it doesn't work for me without explicit car. I have tried it couple of minutes ago. Without getting the car of the list, class-id-slot-name returns "id" instead of :key value that dao-keys "extracts" from the dao class... I'm still a beginner in weblocks and common lisp, so that could be the reason too... > Thanks for bringing the dao-table-name issue to light. I'll get that > committed to my fork with credit to you this afternoon if that's > alright. No problem. I don't care for taking credits so much, I'd just like to see it working well. :-) -- You received this message because you are subscribed to the Google Groups "weblocks" group. 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.
