The @kwaeri/mysql-database-driver component for the @kwaeri/node-kit application platform
- The Implementation
- Getting Started
- How to Contribute Code
- Other Ways to Contribute
@kwaeri/mysql-database-driver reinvents and modernizes the mysql-database-driver portion of the nk application platform.
As the mysql-database-driver component was originally baked into the nk module, its usage was entirely controlled by it. As we discern the process for decoupling the individual components which make up a kwaeri application, we'll begin to simplify the act of doing so, and provide documentation for utilizing each component individually.
The documentation is continually deployed, and located at the Gitlab Hosted Documentation for @kwaeri/mysql-database-driver
@kwaeri/node-kit wraps the various components under the kwaeri scope necessary for building a kwaeri application, and provides a single entry point for easing the process of building a kwaeri application.
However, if you wish to install @kwaeri/mysql-database-driver and utilize it specifically - perform the following steps to get started:
npm install @kwaeri/mysql-database-driver
Include the Component
To leverage the database mysql-database-driver, you'll first need to include it:
Provide a configuration
In order to instantiate a database object, you'll need to provide a configuration of type
Using the Provided mysql-database-drivers
Once you've updated the properties with the correct values for your database instance, supply the configuration to the mysql-database-driver's constructor:
let dbo = conf ;
We have not disclosed every way in which the MySQLDriver package may be leveraged - but as the majority usage of the component will be in calling its object's
query() method, an example of its usage is provided:
Query the Database
An example of querying the database with the provided MySQL database driver:
;// Always catch errors when expecting a promise. You// could use traditional async/await like here, or// go the traditional route.trycatch error
How the return is structured is dependent on the mysql driver implementation, but this is typically how it should be.
As mentioned earlier, the plan is to continue development of the individual components of a kwaeri application - the mysql-database-driver component included - and ultimately ease the process of making use of each individual component as they are decoupled from one another.
More documentation to come!
How to Contribute Code
Our Open Source projects are always open to contribution. If you'd like to cocntribute, all we ask is that you follow the guidelines for contributions, which can be found at the Massively Modified Wiki
Other Ways to Contribute
There are other ways to contribute to the project other than with code. Consider testing the software, or in case you've found an Bug - please report it. You can also support the project monetarly through donations via PayPal.
Regardless of how you'd like to contribute, you can also find in-depth information for how to do so at the Massively Modified Wiki
To submit bug reports, request enhancements, and/or new features - please make use of the issues system baked-in to our source control project space at Gitlab
You may optionally start an issue, track, and manage it via email by sending an email to our project's support desk.
For more in-depth documentation on the process of submitting bug reports, please visit the Massively Modified Wiki on Bug Reports
Our Vulnerability Reporting process is very similar to Gitlab's. In fact, you could say its a fork.
To submit vulnerability reports, please email our Security Group. We will try to acknowledge receipt of said vulnerability by the next business day, and to also provide regular updates about our progress. If you are curious about the status of your report feel free to email us again. If you wish to encrypt your disclosure email, like with gitlab - please email us to ask for our GPG Key.
Please refrain from requesting compensation for reporting vulnerabilities. We will publicly acknowledge your responsible disclosure, if you request us to do so. We will also try to make the confidential issue public after the vulnerability is announced.
You are not allowed, and will not be able, to search for vulnerabilities on Gitlab.com. As our software is open source, you may download a copy of the source and test against that.
When a vulnerability is discovered, we create a [confidential issue] to track it internally. Security patches will be pushed to private branches and eventually merged into a
security branch. Security issues that are not vulnerabilites can be seen on our public issue tracker.
For more in-depth information regarding vulnerability reports, confidentiality, and our practices; Please visit the Massively Modified Wiki on Vulnerability
If you cannot contribute time or energy to neither the code base, documentation, nor community support; please consider making a monetary contribution which is extremely useful for maintaining the Massively Modified network and all the goodies offered free to the public.