why isn't querying jdbc-compliant database seer easy pie?
ok, it's almost easy cake already. nonetheless unequivocally should easier is.
i cruise i should means bond another database only putting jdbc tie twine tnsnames. each database businessman type-4 jdbc engineer there's wholly good, giveaway alternative.
with seer being such penetrating java fans, jvm built-in database i'd have guess jdbc-based fasten record have no-brainer. seems healthy progression have jdbc tie twine tnsnames all "just work" - "sql*plus" anything.
but doesn't work way. wish bond another non-oracle database have buy something called seer gateways disaster around odbc (through something called general connectivity).
[originality warning... associated cave nonetheless someone suggested i enter extra critique removed question. am i argue?]
Comments
Post a Comment