Making backends for data bases is complex, as it covers a wide range of different databases and languages. A project like this would have to start with only a few of the most popular backends. We are currently considering a “connectivity” project that will do some of this.
An error occurred while saving the commenttarun commented
Thanks for your reply. Yes i understand databases live on the server. But so does CSV's. There are only handful of widely accepted databases on the planet ( Oracle, SQL server, MySQL) and handful of languages (java, variants of c, python). You should atleast write the wrapper for these and go from there.
You need to realize that you have built an excellent charting library, but the process of feeding data, is very cumbersome and requires a huge amount of development effort. You should do everything possible to make your product as much easily ingestible as possible.
Also , and i know i am stating the obvious, but most of the worlds data, resides in the databases. Whatever one wants to visualize, is sitting in a database table somewhere. If you want to make them write code to create 2 dimensional arrays for each series and points and axis, it will make more difficult to use your product fluently. Atleast whenever I think of creating a chart, its always the data ingestion process that makes it extremely difficult.