> I can just make a backup copy under a new name when I run the tool to
> create a diff. That way I have the copy available for the next run of
> the script.

Ok, I see your standpoint. And it doesn't look like a correct way for
me.
What I'm thinking is that using migrations should satisfy following
requirements:
1) each VCS (svn, csv, whatever...) revision should be atomic. So each
migrations between any two revisions should describe the same changes
that were done in the schema. So, e.g. changing schema in one
revision, but migration in a following one should be restricted. This
is mostly about development culture.
2) migrations generator should be able to re-generate migrations. So
if you run the generator again, it should generate a migration that
will satisfy requirement #1. A generated migration should overwrite
migration for current svn revision.
3) it should be handy and maximally automatic. What you're saying
about - to make backup files - seems messy to me. Unfortunately I must
admit I would use `schema-diff schema.yml .svn/text-base/
schema.yml.svn-base` instead of your way. As I would say, it's the
least of evils :) Probably some script would do backing up, but again,
it should follow the requirement #1, so as I see something like svn
keyword $id: $ will be a must some way.

Please don't get me wrong. I'm trying to find out a most usable way :)
Actually I don't want to rely on svn, but it seems natural to me to
make migrations act this way.

This all is because have no basis which we should compare our altered
schema with.

> > And how are you going to contribute to doctrine?
> Not sure what you mean. I have svn access.

That's exactly what I meant. Thanks.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to