# Heads up: first spike of kotlin.jdbc available

**URL:** <https://discuss.kotlinlang.org/t/heads-up-first-spike-of-kotlin-jdbc-available/1263>\
**Category:** Uncategorized\
**Created:** [March 13, 2012, 10:14am UTC](https://discuss.kotlinlang.org/t/heads-up-first-spike-of-kotlin-jdbc-available/1263 "2012-03-13T10:14:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jstrachan](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/jstrachan/32/1559_2.png) [@jstrachan](https://discuss.kotlinlang.org/u/jstrachan)\
**Post date:** [March 13, 2012, 10:14am UTC](https://discuss.kotlinlang.org/t/heads-up-first-spike-of-kotlin-jdbc-available/1263/1 "2012-03-13T10:14:13Z")

</div>

There's now a kotlin.jdbc package available (see the [kotlin.jdbc](http://jetbrains.github.com/kotlin/versions/snapshot/apidocs/kotlin/jdbc/package-summary.html) package in the [API docs](http://jetbrains.github.com/kotlin/versions/snapshot/apidocs/index.html)) which has some extension functions for working with JDBC.

Its in no way finshed but you can see the kinds of things possible in this [test case](https://github.com/JetBrains/kotlin/blob/master/libraries/kotlin-jdbc/src/test/kotlin/test/kotlin/jdbc/JdbcTest.kt#L11). The kotlin-jdbc API lets you use functions to be able to properly pool Connections / Statements and handle ResultSets properly without worrying about manual cleanup code etc. You can also iterate through result sets directly with a for loop and use index based or name based access into result sets etc.