It's harder than that. :-) In general, to coordinate two transactional systems, you need a transaction coordinator, like Microsoft's DTC or the ones baked into various JEE containers. And that is what you are talking about here: the Tx system in Clojure + the Tx system in a database.
Good news is that true coordination is not always needed. Better news is that Rich may have something in mind, per his recent comment about UUID in the source code. > I'm really interested in how you would coordinate a database > transaction with an STM transaction. Do you message an agent to do > the database update? > > On Mon, Nov 17, 2008 at 6:13 AM, Stuart Halloway > <[EMAIL PROTECTED]> wrote: >> >> Hi Brian, >> >> The libraries chapter will cover a bunch of different libraries in >> Clojure-Contrib and elsewhere. Obviously, being only one chapter, it >> won't go terribly deep. I'd love to hear what folks want to see. I am >> planning on at least: >> >> * db >> * web apps >> * testing/BDD >> * zipper >> >>> >>> Stuart: >>> >>> I read through the table of contents. Are you planning on addressing >>> interacting with a database (preferably postgres or mysql) in >>> Clojure? >>> >>> Maybe the "Working with Java" chapter will be sufficient, but one of >>> the benefits of Clojure is "batteries included", so helping folks >>> get >>> up to speed with a db example would be great. >>> >>> Brian >>> >>>> >> >> >>> >> > > > > -- > Howard M. Lewis Ship > > Creator Apache Tapestry and Apache HiveMind > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
