Yes, that would be the bit I forgot to include. The failure message would easily be able to include the XML snippet for the database/driver that needed to be added to dbloader.xml and instructions for doing so.

-Eric

Andrew Petro wrote:
Eric,

+1.

I almost suggested here adding a -f flag to "force" it to do the legacy behavior of trying without mappings, I think I'd much rather see any effort applied to giving it a really good failure message telling folks what they're missing and what to do about it.

Andrew


Eric Dalquist wrote:
I'd like to make some small changes to the behavior of DbLoader and DbTest for the 3.0 release. I've seen a large number of problems due to users not having the correct database mappings in dbloader.xml. I would like both the DbLoader and DbTest ant tasks to fail if no match is found. While this may cause a few more headaches on the few databases that don't need mappings it will be much clearer as to what needs to be done for those that do.

Thoughts/Votes?

-Eric


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to