I have written a conform application which connects to a database on our corporate network. I created the database because I was writing the application. Now it is time to document this schema and to provide a method of entertainment in this event that it has been lost for some reason.
I am thinking that the client application should ask the user whether to recreate or provide new connection parameters. Note: The current connection parameters are kept in the obscure text file, which is included in the application setup.
What's best for storing the entertainment or schema of the database is whether the schema should only be placed in a text file in the application directory, or it should be embedded in the app as a string resource.
Besides, is anyone aware of an open source application that I could use to document the database?
Thank you for any help or direction
Perhaps a form of resource Schema should be embedded within the application I am thinking because you have said that the connection parameters have been ambiguous, which states that you do not want the user to have a real knowledge of the database. Providing a schema in the form of a plain text file will give them a fair estimate of what the connection parameters are. Another easy way to recreate the database is to keep an empty copy embedded as an application resource. Rather than recreating the database, you can easily stream this copy.
To document the schema (your second question, in the future, please ask completely different questions), I'm not really sure what you mean you have tables within your database Want to write more lines?
Comments
Post a Comment