Versioning databases? (was General - Version questiosn?)

[William Nagel <bi...@stagelogic.com>]

On Nov 4, 2005, at 9:27 AM, Anastasios Angelidis wrote:

> Next topic in order :D
>
> I'm thinking of scripting every element of a db: tables, stored  
> procs, functions, views for a particular project/component in their  
> own individual .sql files. To much maintenance?
>
> How do you guys go about this? c/c++, java etc... applications are  
> to easy to version! How about the database?

My own work doesn't involve much database-related work, so you should  
take any advice I have with a grain of salt.  That said, it seems to  
me that you should treat your database stuff the same way you would  
any other source files.  Version the SQL files (in whatever  
granularity makes sense to your development process) and then also  
version whatever scripts are necessary to build functioning databases  
from those SQL files.  That way you can just check out the repository  
and run a script to build databases for release or testing.

Second, a bit of general mailing list advice:  Whenever you start a  
new topic make sure you start it with a fresh email instead of by  
replying to another thread (even if that thread is one that you  
started).  In addition to assuring that everyone's mail client will  
thread them properly, you make sure that you maximize the number of  
people who see the new topic.  There may be people who could answer  
your new question who will never see it because they didn't care  
about the old topic and so are ignoring the thread.

-Bill

>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Versioning databases? (was General - Version questiosn?)

[Anastasios Angelidis <vo...@videotron.ca>]

William Nagel wrote:

> On Nov 4, 2005, at 9:27 AM, Anastasios Angelidis wrote:
>
>> Next topic in order :D
>>
>> I'm thinking of scripting every element of a db: tables, stored  
>> procs, functions, views for a particular project/component in their  
>> own individual .sql files. To much maintenance?
>>
>> How do you guys go about this? c/c++, java etc... applications are  
>> to easy to version! How about the database?
>
>
> My own work doesn't involve much database-related work, so you should  
> take any advice I have with a grain of salt.  That said, it seems to  
> me that you should treat your database stuff the same way you would  
> any other source files.  Version the SQL files (in whatever  
> granularity makes sense to your development process) and then also  
> version whatever scripts are necessary to build functioning databases  
> from those SQL files.  That way you can just check out the repository  
> and run a script to build databases for release or testing.
>
> Second, a bit of general mailing list advice:  Whenever you start a  
> new topic make sure you start it with a fresh email instead of by  
> replying to another thread (even if that thread is one that you  
> started).  In addition to assuring that everyone's mail client will  
> thread them properly, you make sure that you maximize the number of  
> people who see the new topic.  There may be people who could answer  
> your new question who will never see it because they didn't care  
> about the old topic and so are ignoring the thread.

Oh I just put general for something that is more version control related 
then subversion related. Thats all.

>
> -Bill
>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org