DAO design pattern

I have 2 DB's (sybase & oracle). I need to pull information from both of them and put it in another DB- table (may be oracle). I am planning to implement DAO and here is my problem:-1. ShouldI use 2 DAO's for two DB- tables? or just one is sufficient using a DAO factory?
[291 byte] By [PaviEluri20a] at [2007-11-27 9:02:00]
# 1
Multi-Post: http://forum.java.sun.com/thread.jspa?messageID=9740736
es5f2000a at 2007-7-12 21:32:09 > top of Java-index,Other Topics,Patterns & OO Design...
# 2
> Multi-Post:> http://forum.java.sun.com/thread.jspa?messageID=974073Recursive rebuke
georgemca at 2007-7-12 21:32:09 > top of Java-index,Other Topics,Patterns & OO Design...
# 3
The point of a DAO is to abstract client code away from the details of your underlying storage. Having two is contrary to this, since client code now has some awareness of the storage. Use oneAnd don't cross-post! :-)
georgemca at 2007-7-12 21:32:09 > top of Java-index,Other Topics,Patterns & OO Design...
# 4
Thank you very much for your contribution.
PaviEluri20a at 2007-7-12 21:32:09 > top of Java-index,Other Topics,Patterns & OO Design...