It would be a good idea to implement something for usage tracking and security updates... I'm sure a DB driver could have security issues.
It would be a good idea to implement something for usage tracking and security updates... I'm sure a DB driver could have security issues.
Comments
Comment #1
aaaristo commentedI'm not sure of what you are proposing to do... Can you be more specific, please?
Comment #2
hass commentedNormally the update module phones home to drupal.org and check out if there are newer releases available. With this functionality a site owner is informed about newer releases and warned if there are security updates available for a module. It also fills the usage statistics on d.o to give all of us an idea about the popularity of a module.
But a driver is not a module... And therefore this data is not collected and update modile does not look for newer versions of the dbdriver... We need to implement a helper module in the db driver to do this job... Or update module need to change in future
Comment #3
aaaristo commentedAaaa ok, i'm actually implementing that helper module mainly to give an administration interface to the driver and to give users a way to inspect performances of queries on Oracle and also to implements some Views hooks we need to override some handler. I can than document it for user to inform them that by enabling this helper module they will have updates and security notifications. So it will be there soon. Thanks you for pointing out the thing.
Comment #4
aaaristo commentedThe module is in the last release.