[vnfsdk] marketplace DB pk and name package name unique constrained.
Hi,
I was looking on the marketplace project and I have same suggestions for issues I notice.
- The package table definition is missing a PK (on the csarid).
- I thinks the package name should have unique constrained.
- Currently the name of the package is taken from the upload zip name. I thinks It should take as an input from the user then uploading the as CASR and I mention before it should be unique so the business code should return an error in case it is not unique .
I will glad to hear your opinions and help with the implantation.
Thanks
Isaac Glick
Isaac Glick,
Thank you for your suggestions.
We will surely work on them. (Uniqueness of package metadata)
All these suggestions will be tracked and will be part of Beijing release.
With regards,
Murali
Sent: 26 December 2017 15:01
To: onap-discuss@...
Cc: Moshe Hoadley <Moshe.Hoadley@...>
Subject: [onap-discuss] [vnfsdk] marketplace DB pk and name package name unique constrained.
Hi,
I was looking on the marketplace project and I have same suggestions for issues I notice.
- The package table definition is missing a PK (on the csarid).
- I thinks the package name should have unique constrained.
- Currently the name of the package is taken from the upload zip name. I thinks It should take as an input from the user then uploading the as CASR and I mention before it should be unique so the business code should return an error in case it is not unique .
I will glad to hear your opinions and help with the implantation.
Thanks
Isaac Glick
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer