-
-
Notifications
You must be signed in to change notification settings - Fork 705
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.
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
[WMS][12.0] - stock_location_zone - alpha version #653
Merged
Commits on Jul 12, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 3f4f540 - Browse repository at this point
Copy the full SHA 3f4f540View commit details
Commits on Jul 15, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 33067e8 - Browse repository at this point
Copy the full SHA 33067e8View commit details
Commits on Aug 15, 2019
-
Configuration menu - View commit details
-
Copy full SHA for d9527d6 - Browse repository at this point
Copy the full SHA d9527d6View commit details
Commits on Aug 27, 2019
-
Add corrections to stock_location_zone
* Allow copy of stock locations (was blocked by constraint on unique name) * Correct loop in _compute_name returning too early if a record had no parent with a 'location_name_format' * Rename field pick_type_id to picking_type_id for coherency * Add missing _description on stock.picking.zone * Correct location_name_format format when the record is a NewId
Configuration menu - View commit details
-
Copy full SHA for 545a8b4 - Browse repository at this point
Copy the full SHA 545a8b4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 00dd814 - Browse repository at this point
Copy the full SHA 00dd814View commit details -
Replace SQL unique constraint by a python one
The new constraints prevents having 2 locations with the same name in the same zone. The SQL UNIQUE constraint was blocking the installation of some addons due to demo data creating, by default, some locations with the same name for the warehouses' locations. Alternative: we could create an INDEX UNIQUE (name, location_id) WHERE picking_zone_id IS NOT NULL But it depends if we want to check the whole tree or not.
Configuration menu - View commit details
-
Copy full SHA for dd28e0e - Browse repository at this point
Copy the full SHA dd28e0eView commit details
Commits on Aug 28, 2019
-
Use unique index for unique location name per zone
The python one was much too slow with large datasets. Here we only check one level (only when the zone is directly assigned), the previous SQL constraint was checking the locations of the same level only anyway.
Configuration menu - View commit details
-
Copy full SHA for 508519a - Browse repository at this point
Copy the full SHA 508519aView commit details -
* Add copyright header * Add myself as contributor of stock_location_zone * Fix lint
Configuration menu - View commit details
-
Copy full SHA for a6998d6 - Browse repository at this point
Copy the full SHA a6998d6View commit details
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.