Modify ↓

Ticket #395 (closed defect: invalid)

Opened 3 years ago

Last modified 23 months ago

forwards()/backwards() should have access to old/new orm

Reported by: rctay89@… Owned by: andrew
Priority: major Milestone: 0.7.1
Component: commands Version: 0.7-rc1
Keywords: Cc:

Description

I do see a prev_orm()/next_orm() method, but as far as I can see, they can't be accessed from forwards()/backwards().

Attachments

Change History

comment:1 Changed 3 years ago by andrew

  • Status changed from new to infoneeded
  • Milestone set to 0.7.1

I don't see what the use case is here - forwards/backwards already get passed an ORM in their parameters, and there should be no concept of a previous/next ORM in data migrations, as there are no schema changes.

comment:2 Changed 3 years ago by andrew

  • Status changed from infoneeded to closed
  • Resolution set to invalid
View ↑

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


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

Attachments ↑
 
Note: See TracTickets for help on using tickets.