>>>>>>>>>>>> Daniel John Debrunner (JIRA) wrote (2006-04-06 18:25:43): > ij is intended as a fairly neutral JDBC client that works against > any database engine. While it may be ok to tailor ij for Derby,
Actually, I think should be an requrement that even if ij is somewhat tailored to Derby, it should remain database independent. That's one of the really nice features of ij. > having to need a specific version of ij to talk to a specific > version of Derby will cause problems. Agree! When testing/experimenting I often find myself having two connections in ij, one to a db from trunk and another which is 10.1. I would consider vetoing an ij tie in to specific Derby versions. > It would be interesting for you to provide a patch that uses the > DatabaseMetData methods directly and displays the resultant > ResultSets using the standard ij code. The we could think about the > "nice layout", what's nice to you maybe horrible to someone else. JDBC should provide enough metadata for this. -- Bernt Marius Johnsen, Database Technology Group, Staff Engineer, Technical Lead Derby/Java DB Sun Microsystems, Trondheim, Norway
signature.asc
Description: Digital signature
