I am curious about what kind of database documentation is provided to you the client (or you as a vendor to the client) when changes are made to the database?
We have a vendor that develops and maintains an application/database, but we do forms and reports in-house. When database changes are made, we get sql scripts and ruby code as documentation for what has changed. While we can read the sql code and can muddle through the ruby code... it's cumbersome to have to sort through 20-30 files sometimes just to understand what is changing.
We really expect to get a little more detail/summarization like a list of tables, columns added/dropped/updated (the change detail... such as datatype from int to bigint or varchar (10) to Varchar(250) ) and the reason why it was changed.
If you are a vendor, what kind of documentation do you provide, for database changes, to the client if they do their own reporting as well? If your client asked for a distinct summary of changes, would you be receptive to their needs?
If you are an end user/client.... what kind of documentation to you get/expect from the vendor, so you don't have to guess at what might break your code?
Thanks for any feedback you might have on this!