...
[11:56:31 CST(-0600)] <dmccallum54> i.e. if the driver keeps ploughing ahead after failed statements, getUpdateCounts wont help
[11:57:59 CST(-0600)] <dmccallum54> cool. sounds like we are agreed, then
[11:58:04 CST(-0600)] <TonyUnicon> yep
[11:58:06 CST(-0600)] <TonyUnicon> thanks
[12:22:11 CST(-0600)] <js70> interesting: https://github.com/42BV/jarb/ https://blog.42.nl/articles/using-database-constraints-in-java/
[12:26:12 CST(-0600)] <js70> so, an outstanding question that I have, we still need a little information to start using the metadata for validation. mainly the table name. that is going to come from the file name correct? headers contain the columnnames and away we go?
[12:27:41 CST(-0600)] <dmccallum54> simplest thing would be for the file names to match table names and file column headers to match db column names
[12:27:57 CST(-0600)] <dmccallum54> the result, of course, is that if the db names change, the file protocol changes
[12:28:22 CST(-0600)] <dmccallum54> but… the advantage is that it's totally obvious how to go from our published spec for the db tables to what your CSV files need to look like
[12:29:08 CST(-0600)] <dmccallum54> so my vote is to try to get as far as we can with unmapped correlations between file/table and column/column names
[12:30:20 CST(-0600)] <js70> k.