Hi, Am Freitag, 5. August 2011 15:56:28 UTC+2 schrieb faenvie: > > so in your case after initial load of the knowledge-base there are no > changes > that need to be persisted, right ? >
Exactly. It's not a running server process or the like. Just a simple small tool. The input data are created elsewhere. following stefan tilkovs book i want to do a simple RESTful > order-management (exercise only) and think of using core.logic > for query-logic. > > persisting changes to rdbms seems not a good idea in case the aim > is to get rid of "OOM/Relational Model impedance mismatch" > In my case a relational db does cut it only in theory. In practise however there are (for various historical reasons, mostly including again the letters S, A and P) inconsistencies in the input data: missing steps in the chain, additional steps in the chain, different part number formats, etc. So it's hard to fit this in tables with some joins. I hope, that I can define relations with core.logic, which help me here. For persistence you could write changes to the an append-only log as fleetdb does. On system start you just rebuild things from the log (and compact the log from time to time). For small applications, this should be sufficient, no? Meikel -- 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 Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
