Yes, a certain level of frustration is bound to occur after you have
spent an hour reading about the project, downloading the code and
setting up an example - only to find a show stopping bug, report it
some time later after finding the right bug tracker... to then notice
that there hasn't
If Migrate is no longer actively maintained then it should be removed
the the SA front page and FAQ (plus other documentation) as it is
quite misleading to direct someone to a moribund project.
--~--~-~--~~~---~--~~
You received this message because you are
On Jul 4, 5:20 am, Noah Slater [EMAIL PROTECTED] wrote:
If Migrate is no longer actively maintained then it should be removed
the the SA front page and FAQ (plus other documentation) as it is
quite misleading to direct someone to a moribund project.
or, someone could spend a week or two
I still think the documentation should be updated - be it help rescue
the Migrate project or whatever. It is misleading not to mention it's
(current) moribund nature.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
So if I change it to say The Migrate project, which is currently
seeking developers, intends to provide schema migration support as
well., would that have prevented whatever frustration you've
experienced ? (since i am sensing frustration).
Yes, a certain level of frustration is bound to
On Jul 4, 2007, at 11:51 AM, Noah Slater wrote:
I still think the documentation should be updated - be it help rescue
the Migrate project or whatever. It is misleading not to mention it's
(current) moribund nature.
OK, i just went to the homepage to re-read whatever big shiny thing I
lets think my real world.
i build a (very) complex tree of objects - the model of the
application data and relations within.
i express this model in some language, implicitly or explicitly,
then, automaticaly (or almost-), map this model into set of db
tables, constraints etc. and this is
Based on the non-responsiveness on the migrate ML, I think migrate
needs someone to take it over at this point. I would favor a rewrite
that doesn't rely upon any monkeypatching within SA (which would have
prevented the breakage upon version change), and I also had agreed
earlier to allow ALTER
I'm still around; unforunately, I'm afraid I lack the time/motivation
to put much more into migrate. I've no objections to someone else
taking over the project, if anyone's interested.
For what it's worth, there's a mostly-finished svn branch that removes
monkeypatching, no changes to SA
