The magic here is the

onCommit

handler in

PersonModel

. It reads the data from the viewmodel after commit and creates a new Person object, which is then inserted into the item property of the viewmodel.

Gotta run now, but I think you've got what you need.

yeah, thank you. I like this approach… I have some data classes from a lib that I wouldn’t like to change and I need to bind them to the wizard.

So your last snippet is perfect for me.. Thank you so much.

This approach seems to work very well to manage a DataSource:

@edvin uploaded a file: Untitled

The

listVendors

function shows how to borrow a connection from the pool and return it once done with a query.

The list function is defined like this in the companion object of

Vendor

@edvin uploaded a file: Untitled

toModel

is called once for each entry in the ResultSet. Vendor then has a constructor that extracts the fields from the ResultSet:

@edvin uploaded a file: Untitled

Don't know if this is the best approach, but it's a start.

The

toModel

function is generic enough that we could even include it in the framework.

I don't know if it's a good idea to have SQL in the Vendor object, maybe that should be moved to the DB controller, but it sure is nice to have the constructor there.

Moving the SQL from the list function in vendor into the DB object first.

These are my CRUD operations so far:

@edvin uploaded a file: Untitled

The reason I kept

prepareStatement

and didn't just do

exec

instead is that IDEA will help you with the SQL inside of a

prepareStatement

function call, so if you make your own extension function on that you loose that ability.

(What I mean by that is that I could have said

exec("DELETE FROM vendor WHERE id = ?") { setInt(1, vendor.id) }

, but then IDEA won't auto complete and verify the SQL.

This isn't about creating yet another SQL framework, just some easy ways to deal with JDBC from TornadoFX.

These are the extension functions I used to make it a little more pleasant:

@edvin uploaded a file: Small JDBC helpers

The SQL highlighting in IntelliJ is a great feature. Sometimes, I see a missed comma in a long list of column names. The names around the missing comma jump out as a different color.

Yeah, I really didn't want to take that away just to save a few keystrokes 🙂

I just love how concise the code has become. This is all it takes to create an editable TableView with save to DB:

@edvin uploaded a file: Untitled

I committed what I had time for tonight, will make this a running show case during the weekend 🙂

These are the interesting bits so far: https://github.com/edvin/tooldb/blob/master/src/main/kotlin/com/cyclestart/tooldb/controllers/DB.kt

I added a progress indicator in the workspace toolbar to show when there is db activity