Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Revert "COV-23 - Added rights for pcmt-integration"

This reverts commit 6c91ae029cb44a10f59c7ba0f2da9c36efde8fe1.

    • -6
    • +0
    ./20200504133506764__add_pcmt_management_rights.sql
COV-23 - Added rights for pcmt-integration

    • -0
    • +6
    ./20200504133506764__add_pcmt_management_rights.sql
OLMIS-6739: Renamed the minimum/maximumToleranceTemperature variables

    • -0
    • +15
    ./20200124111526354__renamed_temperature_columns_in_orderables_table.sql
  1. … 7 more files in changeset.
OLMIS-6739: Renamed the minimum/maximumToleranceTemperature variables

    • -0
    • +15
    ./20200124111526354__renamed_temperature_columns_in_orderables_table.sql
  1. … 7 more files in changeset.
OLMIS-6739: Renamed the minimum/maximumToleranceTemperature variables

    • -0
    • +15
    ./20200124111526354__renamed_temperature_columns_in_orderables_table.sql
  1. … 7 more files in changeset.
OLMIS-6726: renamed the file to fix migrations order

    • -15
    • +0
    ./20200109085441907__add_temperature_and_volume_columns_to_orderables.sql
    • -0
    • +15
    ./20200116085441907__add_temperature_and_volume_columns_to_orderables.sql
OLMIS-6726: renamed the file to fix migrations order

    • -15
    • +0
    ./20200109085441907__add_temperature_and_volume_columns_to_orderables.sql
    • -0
    • +15
    ./20200116085441907__add_temperature_and_volume_columns_to_orderables.sql
OLMIS-6726: Added volume and temperature info to Orderables

    • -0
    • +15
    ./20200109085441907__add_temperature_and_volume_columns_to_orderables.sql
  1. … 21 more files in changeset.
OLMIS-6726: Added volume and temperature info to Orderables

    • -0
    • +15
    ./20200109085441907__add_temperature_and_volume_columns_to_orderables.sql
  1. … 21 more files in changeset.
OLMIS-6726: Added volume and temperature info to Orderables

    • -0
    • +15
    ./20200109085441907__add_temperature_and_volume_columns_to_orderables.sql
  1. … 13 more files in changeset.
OLMIS-6676: Updated lot validator to allow trade items to share lot codes. Also added unique constraint...
OLMIS-6676: Updated lot validator to allow trade items to share lot codes. Also added unique constraint...
OLMIS-6676: Updated lot validator to allow trade items to share lot codes. Also added unique constraint in the database.

    • -0
    • +6
    ./20200110104748702__enable_trade_items_to_share_lot_codes.sql
  1. … 6 more files in changeset.
AO-379 Add new 'lots manage' right for lot endpoints.

AO-379 Add new 'lots manage' right for lot endpoints.

    • -0
    • +4
    ./20190726083236971__added_lots_manage_right.sql
  1. … 4 more files in changeset.
AO-379 Change changelog ticket link to core one and remove comments.

    • -7
    • +0
    ./20190726083236971__added_lots_manage_right.sql
  1. … 1 more file in changeset.
AO-379 Add migration for lots manage right creating.

    • -0
    • +11
    ./20190726083236971__added_lots_manage_right.sql
OLMIS-6402: Renamed versionId to versionNumber in referencedata
OLMIS-6402: Renamed versionId to versionNumber in referencedata
OLMIS-6402: Renamed migration

    • -27
    • +0
    ./20190722091929982__rename_versionId_to_versionName.sql
    • -0
    • +27
    ./20190722091929982__rename_versionId_to_versionNumber.sql
OLMIS-6402: Renamed versionId field to versionNumber

    • -0
    • +27
    ./20190722091929982__rename_versionId_to_versionName.sql
  1. … 43 more files in changeset.
removed

removed

Yes. The table can contain a lot of data so adding columns and set default values could drop performance

Yes. The table can contain a lot of data so adding columns and set default values could drop performance

Is it because dropping and recreating is faster?

Is it because dropping and recreating is faster?

I don't think we should be settings this in the constructor. I might want to use this constructor in retrieval endpoints, for example Isn't doing this in PrePersist/Update annotated method enough?

I don't think we should be settings this in the constructor. I might want to use this constructor in retrieval endpoints, for example

Isn't doing this in PrePersist/Update annotated method enough?