Evolution prompting for user input.

[Stavros]

Hello,
is there a way for an evolution to prompt for user input instead of
relying on default values, which are hard to push to production?

I have a feeling I'm not using evolution's workflow correctly, what
would be the preferred way to deal with values requiring user input?

[Russell Keith-Magee]

On Sun, Apr 12, 2009 at 12:57 AM, Stavros <poro...@gmail.com> wrote:
>
> Hello,
> is there a way for an evolution to prompt for user input instead of
> relying on default values, which are hard to push to production?

No - this is by design.

> I have a feeling I'm not using evolution's workflow correctly, what
> would be the preferred way to deal with values requiring user input?

Your feeling is correct.

Part of the design goal for Django Evolution is to provide a clear
audit trail for the changes that have been made to the database over
time. Part of this audit trail is a sequence of stored evolutions that
are on the file system.

Using stored evolutions has two advantages:
1) It ensures that all developers are applying the same evolution sequence
2) It allows you to specify any initial value you want.

While it is possible to execute the --hint'ed evolution, the hinting
process isn't intended as the normal way of performing evolutions. As
a result, the capabilities of the hinting system are limited - they
are sufficient for really simple cases, but not much beyond that.

Yours,
Russ Magee %-)