I'm starting to incrementally merge from r3647 back to trunk fixing things along the way.
victor "i ♡ source control" ng
On 11/7/06, Victor Ng
<[EMAIL PROTECTED]> wrote:
Hi all,
I've got time at work to work on the schema evolution branch and to
make sure that it works properly and to get it properly synced up to
django's SVN head.
From what I can see - the latest merge from trunk to the schema
evolution branch has caused quite a lot of code breakage - can anyone
else verify this?
I'm testing everything using the postgresql_psycopg2 backend for now.
I'm getting a couple postgresql errors in branch revision r3647 which
are related to tzinfo_factory settings in psycopg2 driver, but those
are easy to fix.
I can't get the tests to work at all using branch revision r3937. I get this:
---
> python tests/runtests.py --settings= schematests.settings
Traceback (most recent call last):
File "tests/runtests.py", line 138, in ?
django_tests(int(options.verbosity), args)
File "tests/runtests.py", line 117, in django_tests
run_tests(test_models, verbosity, extra_tests=extra_tests)
File "/usr/local/lib/python2.4/site-packages/django/test/simple.py",
line 81, in run_tests
management.syncdb(verbosity, interactive=False)
File "/usr/local/lib/python2.4/site-packages/django/core/management.py",
line 717, in syncdb
for sql in get_sql_evolution(app):
File "/usr/local/lib/python2.4/site-packages/django/core/management.py",
line 462, in get_sql_evolution
output = get_sql_evolution_check_for_changed_field_flags(klass,
new_table_name)
File "/usr/local/lib/python2.4/site-packages/django/core/management.py",
line 570, in get_sql_evolution_check_for_changed_field_flags
existing_fields = introspection.get_columns(cursor,db_table)
AttributeError: 'module' object has no attribute 'get_columns'
---
Can anyone else verify this problem? If this is the case, I'm going
rebranch from r3647 on my local repository and merge back to trunk
incrementally.
thanks,
vic
On 11/6/06, Victor Ng < [EMAIL PROTECTED]> wrote:
> What problems have you had with schema evolution?
>
> We're pretty commited to using Django over at my company - and I need
> schema evolution badly - so I'll be starting to kick the s-o branch
> starting tomorrow afternoon to see if it's stable enough for us.
>
> If necessary, I can apply patches myself as I'm running an instance of
> svk that mirrors the entire django source tree anyway.
>
> vic
>
> On 11/6/06, Matthew Flanagan < [EMAIL PROTECTED]> wrote:
> >
> >
> > I don't think any of those proposals reflect what is actually
> > implemented. I've used the schema-evolution branch and have had some
> > issues which are yet to be resolved or even responded to by the
> > developer.
> >
>
>
> --
> "Never attribute to malice that which can be adequately explained by
> stupidity." - Hanlon's Razor
>
--
"Never attribute to malice that which can be adequately explained by
stupidity." - Hanlon's Razor
--
"Never attribute to malice that which can be adequately explained by stupidity." - Hanlon's Razor
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
