Table Copy

Just did a utility class in Java that takes two tables, a field map, and two connections in order to copy data from one db to another. It’s probably fairly buggy and I’m once again wondering, why I have to implement such helpers, they should be around. Which led me to another thought. These days you are most likely to use some OR-Mapping and then do the stuff in your OO-Model. It seems that this doesn’t fit the bill with all the deployment and upgrade needs of a real world app. Probably we need some more abstraction on the Databaselayer just like the aforementioned TableCopy class.






Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.