Knut Anders Hatlen <[email protected]> writes: > java org.apache.derby.tools.dblook -d jdbc:derby:db | java > -Dij.database="jdbc:derby:copy;create=true" org.apache.derby.tools.ij > > This would stop working if "CONNECT 'jdbc:derby:db';" had been added to > the output. > I agree that we should not add the passwords to the output. To keep it > simple in the first iteration, we could perhaps just print a comment > stating that the statements below need to be executed as user X in order > to get the exact same dependencies as in the original database. That's > consistent with what dblook currently does for the initial connection, > it prints the URL in a header comment instead of printing a CONNECT > statement.
Right, but sooner or later we do need to be able to establish connections for different users somehow. Emitting these in comments for the time being is fine, I think. Maybe we will need to tweak ij a bit. > > > If we later find an elegant solution to this problem, it should be > fairly easy to replace the comment with whatever we come up with. But I > don't think the lack of an elegant solution at this point is a > showstopper, as printing the DDL in sorted order would be a great > improvement by itself. +1 Dag
