# Some useful changes to the mysql node

**URL:** https://discourse.nodered.org/t/some-useful-changes-to-the-mysql-node/20884
**Category:** Share Your Nodes
**Created:** [26 January 2020 21:16 UTC](https://discourse.nodered.org/t/some-useful-changes-to-the-mysql-node/20884 "2020-01-26T21:16:02Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![kuema](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kuema/32/6542_2.png) [@kuema](https://discourse.nodered.org/u/kuema)
#### Post date: [27 January 2020 05:55 UTC](https://discourse.nodered.org/t/some-useful-changes-to-the-mysql-node/20884/3 "2020-01-27T05:55:45Z")

</div>

Just a thought, but would using the `tls-config` config node be an option? It is already provided by the core.

Here's my previous post about that:

> [@\[Announce\] node-red-contrib-homie-convention](https://discourse.nodered.org/t/announce-node-red-contrib-homie-convention/16329/7):
>
> The TLS config node is provided by the core as tls-config, so you can use it like any other config node. So I think all you need to do is just add an optional node property, like tls: {type:"tls-config",required: false} The core MQTT node is a good example.

---

_[View the full topic](https://discourse.nodered.org/t/some-useful-changes-to-the-mysql-node/20884)._