Updateable ResultSet just for doing inserts: good idea?

[Jesper Ottosson]

I hate it when my INSERT statements become horribly long. One thing that would solve this is querying for an empty updateable resultset from the table i want to insert into, and then use the update methods to specify the values (after doing a moveToInsertRow)
Is this a good idea, or does it have serious performance implications?
/ Jesper

[Jamie Robertson]

I find that PreparedStatements clean up a long insert statement:

String insert = "insert into emp values ( ?, ?, ?, ?, ?, ..., ? )
...
ps.setString(1, text1);
ps.setString(2, text2);
ps.setString(3, text3);
...

instead of

String insert = "insert into bigMessyTable values ('" + text1 +"', '" +
text2 + "', '" + text3 + "', " + ....

I'm not a big fan of scrollable/updateable resultsets, but you could query your table for an empty ResultSet:
"select * from emp where 1=2"...then move to insert row...etc
but I'm not sure if you can have a where clause on the resultset if you want to insert into it(some drivers/DB's throw exceptions)

Jamie