Actually, the source database is a wierd beast called Versant. It's rather an object persistence store than a database, and it is non-relational.

When it comes to locking strategies, Versant tends to assume that you know what you are doing (something which was not the case in this instance).

Why not have the one database dump its table using its native tools?

That's a thought. The client where I am working do tend to have a philosophy of doing everything in application code (C++, yeugh). I looked at

db2tty -D $DBAME -i myClass
[download]

and this does dump all objects in myClass to stdout. There are issues with escaping and format conversion, and it would be hard to convince my colleagues to abandon the extractor code they are already using.

Anyone else out there using Versant?

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.