enhancement Permission/Setting to enable/disable Database Direct Select only restriction ESP Build 3237

[Martyn Houghton]

Can I request an enhancement to allow the restriction introduced in ESP Build 3237 - "Enforced checks for Database Direct to only allow SELECTs for production instances" to be configurable by a permission or system setting, as we often use additional SQL commands in the Admin Tool Database Direct to correct or update records especially when undertaking data migrations into our Hornbill Instance.

Cheers

Martyn

 

 

[Martyn Houghton]

Examples

 

[Victor]

@Martyn Houghton unlikely that we would implement this. We would be interested to know where do you have the need to run INSERT or UPDATE statements other than following the org import (which is being discussed separately).

If there is a need to run INSERT or UPDATE then it means there is a lack of functionality somewhere or some existing functionality does not work as intended, which needs to be looked at product managers and/or development team.

There should be no need for any user to run UPDATE or INSERT statements in a customer/production instance.

[Martyn Houghton]

@Victor

The issue is is that we are doing live migrations as we speak and the next three weeks, so we will need a method to get these updates done now rather than having to wait for the updated tools.

Therefore we will need to pass these to yourselves to run on our instances, if the restriction is not removed or made configurable.

In our test transfer we where able to do these updates and the ESP build change was done without warning.

Cheers

Martyn

[Victor]

@Martyn Houghton - I will raise a support request to sort out the issues you are having for running the import tool including additional actions you need performed for this import (such as subscriptions)

[Martyn Houghton]

@Victor

Thanks.

Cheers

Martyn

[Alberto M]

@Victor, we used to run a few UPDATE and INSERT scripts from time to time. 

If you say "If there is a need to run INSERT or UPDATE then it means there is a lack of functionality somewhere or some existing functionality does not work as intended, which needs to be looked at product managers and/or development team.", what will be the best way to share with you our needs for running those scripts?

 

(Sorry to hijack your post, @Martyn Houghton )

[Victor]

@Alberto M basically the place to discuss these things is right here, on our forums. If you need to run UPDATE and/or INSERT then it mees somewhere there is some functionality missing. It can possibly mean that something is actually broken.