Now what I really need is beta testers. I don't expect anyone to use it in production, but it would be great if you could try it with any existing application by just placing the .jar on the class path, changing the connection string, and running your test suites/load tests etc. Report any issues to me at launchpad.
Also, I need some inspiration, are there any features you have wanted to see in a JDBC driver? Cloud aware (if anyone wants this, please define it for me :) )? Plug-in system for query optimization etc?
How to help:
- Download Drizzle-JDBC 0.7 and place it on your classpath, or, if you use maven, add this dependency to your pom.xml:
<dependency> <groupId>org.drizzle.jdbc</groupId> <artifactId>drizzle-jdbc</artifactId> <version>0.7</version> </dependency>
- Change the connection string to the form:
jdbc:mysql:thin://<username>:<password>@<hostname>:<port>/<schema>
(if your tooling needs to do a Class.forName, the driver classname is org.drizzle.jdbc.DrizzleDriver)
- Run your test suite
- When anything unexpected happens, post a bug report at launchpad, preferably with a stack trace and the test case that triggered the error (or send me an email at krummas@gmail.com if you don't have a launchpad account and don't want one).
6 comments:
What is the driver?
org.drizzle.jdbc.DrizzleDriver
(i also did not find it on the wiki)
Hi
You can download it from the maven repository, http://repo2.maven.org/maven2/org/drizzle/jdbc/drizzle-jdbc/0.7/drizzle-jdbc-0.7.jar
Hope it helps
Or, not sure i understand the question, what is the problem?
Next to the jar and the connection string, users need to know the driver class. This seemed to be missing from this blog and the wiki.
Since drizzle jdbc is only for java6, the driver class name is not really needed (it auto registers)
Guess some tools/frameworks might need it though, ill update the post, thanks
Post a Comment