On Wed, Dec 17, 2008 at 11:00 AM, Scott Jaderholm <jaderh...@gmail.com> wrote: > Thanks for the idea. Although those are definitely necessary steps, > unfortunately the problem still persists. >
Can you get a similar Java program work correctly? i.e. we want to try and separate if this is specific to JDBC in Clojure or JDBC on its own. Another thing to consider is that the full stack trace may provide some clues as to what is really going on. From the REPL you can refer to the most-recent exception with the *e (or . To get the full stacktrace at the REPL: (.printStackTrace *e *err*) /mike. --~--~---------~--~----~------------~-------~--~----~ 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 clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
