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.

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
merged 8 commits into from
Sep 11, 2019

Commits on Jul 12, 2019

  1. [ADD] stock_location_zone

    jbaudoux committed Jul 12, 2019
    Configuration menu
    Copy the full SHA
    3f4f540 View commit details
    Browse the repository at this point in the history

Commits on Jul 15, 2019

  1. [ADD] stock_location_zone

    jbaudoux committed Jul 15, 2019
    Configuration menu
    Copy the full SHA
    33067e8 View commit details
    Browse the repository at this point in the history

Commits on Aug 15, 2019

  1. Refactoring

    jbaudoux committed Aug 15, 2019
    Configuration menu
    Copy the full SHA
    d9527d6 View commit details
    Browse the repository at this point in the history

Commits on Aug 27, 2019

  1. 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
    guewen committed Aug 27, 2019
    Configuration menu
    Copy the full SHA
    545a8b4 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    00dd814 View commit details
    Browse the repository at this point in the history
  3. 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.
    guewen committed Aug 27, 2019
    Configuration menu
    Copy the full SHA
    dd28e0e View commit details
    Browse the repository at this point in the history

Commits on Aug 28, 2019

  1. 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.
    guewen committed Aug 28, 2019
    Configuration menu
    Copy the full SHA
    508519a View commit details
    Browse the repository at this point in the history
  2. Set Alpha development status

    * Add copyright header
    * Add myself as contributor of stock_location_zone
    * Fix lint
    guewen committed Aug 28, 2019
    Configuration menu
    Copy the full SHA
    a6998d6 View commit details
    Browse the repository at this point in the history