Closed GoogleCodeExporter closed 8 years ago
Matthew,
You're totally right. My intention is to write db-specific script runners, but
I just
haven't gotten around to it. So, what you're seeing is the harness for
handling it.
It's been that way for a while and I haven't gotten around to writing any
db-specific
runners, though I've started working on a Postgres implementation. It just
hasn't
seen any love in a while (and who knows when it will again).
The issue is that different DBs handle proc/func declarations differently. I
was once
of the mindset that instead of a adding complexity to ScriptRunnerImpl for all
of the
cases, I would keep the implementations simple and specific to one DB.
Anyway, thanks for the nudge... I should either implement the next one or get
rid of
the extra layer. -Christian
Original comment by christia...@gmail.com
on 26 Feb 2010 at 9:17
Cleaned up.
Original comment by christia...@gmail.com
on 24 May 2010 at 9:46
Original issue reported on code.google.com by
matthew.mceachen
on 26 Feb 2010 at 9:04