I'm just wondering since it seems the migrations created are all prepended
with an incremental number... so if two developers were to push two
different migrations, each with the same id, I'm afraid something bad will
happen.
For example:
Dev A: creates 001_somedesc
Dev B: creates 001_someother
For that to happen, models would have to be changed without a migration
being generated, or without it boeing added to source control. Neither is
good practice.
On Aug 16, 2012 7:56 AM, "Benjamin Lei" wrote:
> I'm just wondering since it seems the migrations created are all prepended
> with an in
Well, if you push without pulling, this might happen, if you always
pull before pushing, then you'd have to manually merge both migrations
(which would probably mean letting the other migration as 001, and
changing yours so it adds your wanted changes on top of THAT
And as an answer: using south i
On Thu, 2012-08-16 at 10:39 -0300, Tomas Neme wrote:
> Well, if you push without pulling, this might happen,
*Implicit git usage* :D
I'd expect git to squeal about it being a non-fast-forward commit.
--
You received this message because you are subscribed to the Google Groups
"Django users" gr
>> Well, if you push without pulling, this might happen,
>
> *Implicit git usage* :D
Implicit VCS usage, whichever you choose.
If you don't, you shouldn't be doing team work
--
"The whole of Japan is pure invention. There is no such country, there
are no such people" --Oscar Wilde
|_|0|_|
|_|_
>>> Well, if you push without pulling, this might happen,
>>
>> *Implicit git usage* :D
>
> Implicit VCS usage, whichever you choose.
>
> If you don't, you shouldn't be doing team work
ah, I see now. CVS wouldn't complain in that scenario...
neither would git/hg when you pull, for that case.. yes
On Thu, Aug 16, 2012 at 12:44 AM, Benjamin Lei wrote:
> I'm just wondering since it seems the migrations created are all prepended
> with an incremental number... so if two developers were to push two
> different migrations, each with the same id, I'm afraid something bad will
> happen.
>
> For ex
On 08/16/12 08:58, Paul Backhouse wrote:
> On Thu, 2012-08-16 at 10:39 -0300, Tomas Neme wrote:
>> Well, if you push without pulling, this might happen,
>
> *Implicit git usage* :D
>
> I'd expect git to squeal about it being a non-fast-forward commit.
Git should, though other VCSes might notice
8 matches
Mail list logo