Skip to content
This repository has been archived by the owner on Oct 6, 2020. It is now read-only.

tracking number may be null + updated db migration #12

Closed
wants to merge 3 commits into from
Closed

tracking number may be null + updated db migration #12

wants to merge 3 commits into from

Conversation

jarekdz
Copy link
Contributor

@jarekdz jarekdz commented Sep 11, 2014

  • The "tracking_number" field in the ShippingPackage model should allow to store null values.
  • updated db migration

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling 6a16a83 on jarekdz:master into b0abf5d on tangentlabs:master.

@jarekdz
Update abstract_models.py
a2628ec 
fix FulfillmentShipment class unicode method to return string not tuple
@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling a2628ec on jarekdz:master into b0abf5d on tangentlabs:master.

@roadsideseb
Copy link
Contributor

@jarekdz can you explain the scenario that would require NULL instead of an empty string?

@sasha0 sasha0 closed this May 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@jarekdz @coveralls @roadsideseb @sasha0