Rick Hillegas <[email protected]> writes: > Hiranya Jayathilaka wrote: >> Hi Folks, >> >> Now that I've reached the final stages of my project to improve >> dblook I think it's time I start thinking about writing some >> automated tests for the new and improved dblook implementation. Dag >> came up with the idea of getting dblook to generate a script against >> some reference database and then run the script to create a copy of >> the reference database. Then the copy will be compared with the >> reference database to verify that all persistent objects like tables >> and views are properly in place. Eventhough it sounds like lot of
You would also want to check that the permissions and role tables are the same. [Note that the dependency tables might be hard to compare: For example if a view was constructed on the virtue of having a role set, that view would be dependent on the role in the original database. Later, a direct permission to the user in question may have been added. Then, in a reconstructed database, a direct user permission is "preferred" (checked first) when the view is reconstructed and, hence, the dependencies would be different (although otherwise the databases schemas would be the same, and allowed operations would be the same). Such subtle differences would only make a difference when revoking privileges or roles. Ideally the order in which privileges are given should not matter; it only does matter due to DERBY-1632. I think you should ignore this effect for now. :) It may merit a footnote in the (updated) docs for dblook.. ] Dag
