We would like to have the ability to create more advanced queries, which would include an Update, Delete, and Alter (database structure revision) option.
@Guest Thanks for sharing these details which are quite helpful. I agree that the ability to add support to delete records is a good idea and will create a feature in our backlog for that.
For the update request, I would like to mention that today you can create advanced queries and enter edit mode. Once in Edit Mode, you can enter a value in a cell and drag it down in the column or copy it and select a set of cells and paste the value to all records.
With respect to the "Alter" operations you are requesting, we do not plan to enable that through a query because that can potentially introduce breaking changes into the iModel. To make such alterations we advise using OpenPlant Project Administrator to adjust the iModel schemas as needed.
We know these functions are dangerous if one doesn't know what they are doing. Deleting from PlantSight only allows deleting orphaned records, which is usually sufficient. However, there are times when we have a tag that does not conform to the defined format in the parser regular expression. Sometimes, those records are extremely difficult to fix, but if we could delete the record from the component table along with the tables that link the component to a drawing, it would make the process much simpler.
We have also had records that have been deleted from a drawing, but due to some corruption, the record is not removed from PlantSight during synchronization.
@Guest Thanks for sharing these details which are quite helpful. I agree that the ability to add support to delete records is a good idea and will create a feature in our backlog for that.
For the update request, I would like to mention that today you can create advanced queries and enter edit mode. Once in Edit Mode, you can enter a value in a cell and drag it down in the column or copy it and select a set of cells and paste the value to all records.
With respect to the "Alter" operations you are requesting, we do not plan to enable that through a query because that can potentially introduce breaking changes into the iModel. To make such alterations we advise using OpenPlant Project Administrator to adjust the iModel schemas as needed.
We know these functions are dangerous if one doesn't know what they are doing. Deleting from PlantSight only allows deleting orphaned records, which is usually sufficient. However, there are times when we have a tag that does not conform to the defined format in the parser regular expression. Sometimes, those records are extremely difficult to fix, but if we could delete the record from the component table along with the tables that link the component to a drawing, it would make the process much simpler.
We have also had records that have been deleted from a drawing, but due to some corruption, the record is not removed from PlantSight during synchronization.
We're looking to have the ability to perform basic functions that we used to do in SQL Server.
For example, UPDATE pfunc.instrument set COMP_DESC='Magnetic Flowmeter' WHERE COMP_CODE='F04'
OR
ALTER pfunc.instrument add COMP_DESC VARCHAR(40)
OR
ALTER TABLE pfunc.instrument MODIFY COMP_CODE VARCHAR(100)
OR
DELETE FROM pfund.unit WHERE CODEVALUE='OOPS'
@Guest Can you review my comment above and add some clarifications.
Todd, can you provide more details to this request and examples for Update, Delete and Alter that you would be interested in.