Hey there,
Is their a particular reason you wouldn't or couldn't use existing java persistence infrastructure inside your scala application? That's the recommended advice right now; JPA (for instance) will slot right into your app :-) Cheers, Tim On 22/05/2009 20:43, "braver" <delivera...@gmail.com> wrote: > > One of the huge drawbacks in beginning serious use of Scala is the > lack of an accepted and documented way to talk to the databases such > as PostgreSQL. Googling for scala.dbc examples pulls old stuff from > 2007; there's a scala-query on github, which is promising, and > abandoned dbc2, and dbc3 is... awaiting new language features! > > Some of my Scala-DB findings are documented in the blog at > http://la.scala.la/, > and none look satisfactory so far. > > So it looks like the way to do it right here, right now, is down to > Java JDBC. I was glad to see an example of that in @dpp's book. I > wonder if you guys can point to specific idioms of using JDBC with > actors for data-heavy apps such as data mining? Since Lift is the > heavy consumer of DBs, I believe you have the most experience with it! > > Cheers, > Alexy > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
