I'm surprised to see this suggestion of storing a SQLite db in version
control. Don't you quickly run into problems where two developers each
write new data to the database, and then cannot merge their changes? Or
do you have a read-only database?
--Ned.
http://nedbatchelder.com/blog
Brian L
andy baxter wrote:
>
> Not sure if it's quite an answer to your question, but I've been dealing
> with a similar problem which is how to keep the test data I've added to
> the system between (mostly minor) changes to the database. The approach
> I've taken is as follows:
>
> - before making any
Julien wrote:
> Hi,
>
> We're using SVN between several developers to work on the same project
> and it's working quite well. But it's not as simple concerning the
> database.
>
> Each of us has a local database to muck around with, and if one of us
> makes a change in the models that implies modi
On Thu, Apr 3, 2008 at 4:27 AM, Ronny Haryanto <[EMAIL PROTECTED]> wrote:
>
> On Thu, Apr 3, 2008 at 7:36 AM, Julien <[EMAIL PROTECTED]> wrote:
> > We're using SVN between several developers to work on the same project
> > and it's working quite well. But it's not as simple concerning the
>
On Thu, Apr 3, 2008 at 7:36 AM, Julien <[EMAIL PROTECTED]> wrote:
> We're using SVN between several developers to work on the same project
> and it's working quite well. But it's not as simple concerning the
> database.
>
> Each of us has a local database to muck around with, and if one of us
Simon's method is a good way to go. In general its a good idea to use
some sort of scheme for managing all of the changes that occur to the
base schema in revision control. This way you can pull down a tagged
copy of your source tree, run the CREATE DATABASE script, and run the
alter script(s) a
> that developer has to inform all others of the changes so they all
> make the change manually on their own local database.
you could have a mysql-changes.sql file in your app directories. it
holds the ALTER, DROP, etc. statements. put it under SVN. when you get
a new rev with the comment "db ch
Hi,
We're using SVN between several developers to work on the same project
and it's working quite well. But it's not as simple concerning the
database.
Each of us has a local database to muck around with, and if one of us
makes a change in the models that implies modifying the database
manually
8 matches
Mail list logo
