You are correct as I wanted the source and target tables to be in different databases, and so the Chris's solution would have not worked for me.
BTW, I used system procedures to export the data from the source table to a file, and then imported the data from that file to the target table to get the required job done.
The proposed new feature that you referenced will be a welcome addition to the command set of Derby. :)
--- On Mon, 26/4/10, Bryan Pendleton <email@example.com> wrote: