Yep, Class/forName does the job.
I like the consistency of the JVM implementations (glup !), I run on
Ubuntu wih:
java version "1.6.0_03"
Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
Java HotSpot(TM) Server VM (build 1.6.0_03-b05, mixed mode)
I do have the mysql jar file in my classpath
(mysql-connector-java-5.0.8-bin.jar)
like all the 130 or so jar files I use daily and no the driver does not
get registered by magic
Blblblblblblblblbl....
Looking at classForName in the RT.java module (in trunk, checked out a
few days ago):
static public Class classForName(String name) throws
ClassNotFoundException{
return Class.forName(name, false, baseLoader());
}
false means do not initialize the class.
It's faster to avoid the class initialization and it's probably the
proper thing to do 98% of the time.
Make that patch "permanent" in contrib/sql :)). A change in the actual
implementation
would surprise me, too many performance impacts and possible behaviour
problems may rise from a change.
Thank you,
Luc
On Thu, 2008-10-16 at 22:03 -0400, Stephen C. Gilardi wrote:
> Class/forName "com.mysql.jdbc.Driver")
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
