Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Django ORM fixes #296

Merged
merged 2 commits into from
Sep 24, 2015
Merged

Django ORM fixes #296

merged 2 commits into from
Sep 24, 2015

Conversation

Hwesta
Copy link
Contributor

@Hwesta Hwesta commented Sep 24, 2015

  • Init Django in file_to_folder (only used in DSpace path)
  • Make FPCommandOutput use legacy table, instead of creating its own. (@mistydemeo was this done intentionally? My problem was FPCommandOutput seem to disappear when queried at MySQL command line)

@jhsimpson jhsimpson changed the title Misc fixes Django ORM fixes Sep 24, 2015
@jhsimpson
Copy link
Member

I think we need to keep the legacy table name, so existing records are not orphaned, so

👍

@jhsimpson jhsimpson added this to the 1.5.0 milestone Sep 24, 2015
@qubot qubot merged commit ab97a22 into qa/1.x Sep 24, 2015
@qubot qubot deleted the dev/issue-xxxx-fixes branch September 24, 2015 21:50
@Hwesta
Copy link
Contributor Author

Hwesta commented Sep 24, 2015

Double-committed to qa/1.5.x as 0a1152e and 21d223d

@jhsimpson jhsimpson modified the milestones: 1.6.0, 1.5.0 Oct 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.5.0
Development

Successfully merging this pull request may close these issues.
3 participants
@Hwesta @jhsimpson @qubot