Code

Opened 7 years ago

Closed 6 years ago

#5230 closed (wontfix)

[schema-evolution] sqlevolve fails

Reported by: raik.gruenberg@… Owned by: nobody
Component: Database layer (models, ORM) Version: other branch
Severity: Keywords: schemaEvolution
Cc: Triage Stage: Someday/Maybe
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

I just installed the schemaEvolution branch of django (following the instructions on the schemaEvolutionDocumentation site). I added a table and some fields to an existing (and working data model) and then run:

python manage.py sqlevolve repository

But this resulted in the following Error:

BEGIN;
Traceback (most recent call last):
  File "manage.py", line 11, in <module>
    execute_manager(settings)
  File "/usr/lib/python2.5/site-packages/django/core/management.py", line 1886, in execute_manager
    execute_from_command_line(action_mapping, argv)
  File "/usr/lib/python2.5/site-packages/django/core/management.py", line 1845, in execute_from_command_line
    output = action_mapping[action](mod)
  File "/usr/lib/python2.5/site-packages/django/core/management.py", line 512, in get_sql_evolution
    return get_sql_evolution_detailed(app)[2]
  File "/usr/lib/python2.5/site-packages/django/core/management.py", line 550, in get_sql_evolution_detailed
    schema_fingerprint = introspection.get_schema_fingerprint(cursor, app)
AttributeError: 'module' object has no attribute 'get_schema_fingerprint'

My test system is a ubuntu 7.04 server, runs python 2.4 and the database sits in postgresql 8.2.
I can attach the models.py script but the error doesn't look as if it is related to my data...

Attachments (0)

Change History (4)

comment:1 Changed 7 years ago by russellm

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

As fair warning - the schema-evolution branch is a slightly wierd beast. It was introduced for a Google Summer of Code project in 2006, but wasn't merged at the end of that period; recent discussions about the design implemented by the branch suggest that it is unlikely that this branch will be merged in its current form.

I'll leave this ticket open in case Derek (the developer working on the branch) wants to address the issue, but you should be warned that the core developers aren't looking at this branch, either to fix bugs or to coordinate merging to trunk. If a schema-evolution feature comes to Django, it almost certainly won't look like this branch.

comment:2 Changed 7 years ago by Simon G. <dev@…>

  • Summary changed from schemaEvolution sqlevolve fails to [schema-evolution] sqlevolve fails

comment:3 Changed 6 years ago by jacob

  • Triage Stage changed from Unreviewed to Someday/Maybe

comment:4 Changed 6 years ago by Alex

  • Resolution set to wontfix
  • Status changed from new to closed

This branch is not maintained, and will almost definately not be used if/when evolutions make their way into django.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.