Database Connector - Mendix App Store

Database Connector

The Database connector can be used to seamlessly connect to external databases without limiting you in your choice of database or SQL dialect, enabling you to incorporate your external data directly in your Mendix application.
Downloads:2941

Connectors

Database Connector logo5 stars, based on 16 votes
2017-07-04
5/5stars
Very nice app.It is too good.
2017-07-04
5/5stars
I am using DatabaseConnector to retrieve data and stored data from mysql table.It is very useful app
2017-07-19
5/5stars
Hi, I have downloaded and added the module, but I cant see the database connector in the toolbox. There is only the module. I'm using Modeler 7.5. I have followed the documentation for installation, but nothing appears in the toolbox. Thanks
2017-11-02
5/5stars
Handy module to extract data from remote databases.
2018-03-05
5/5stars
A great way to connect to databases.
2018-04-15
5/5stars
Sat with a Business User(with functional structure knowledge of the DB) along with a SQL Colleague who can describe the query while I use this module to trigger it in the matter of minutes. Nice one!
2018-04-17
5/5stars
I am unable to connect to database.Anyone can help
2018-05-21
3/5stars
I installed the module and after some trial and error I have it working on localhost. I want to use it in the staging/[production environment so that will next step... With a query I get the data returned in an object list which must exactly match the database. I would prefer only a list of Strings with comma-separated values or (better) an JSON object. I will mark this on github too. But sofar experiences are ok.
2018-11-16
5/5stars
Very useful for data migration.
2019-01-04
5/5stars
Great tool which extends communication channels from Mendix apps.
2019-02-18
5/5stars
Used it to connect to APS database, worked great
2019-02-21
5/5stars
Great way to enhance the integration capabilities of Mendix
2019-04-25
5/5stars
can not miss in data project
2019-04-30
5/5stars
Thanks for this module, I like it a lot. Although there is only one change I would recommend. In ResultSetIterator.java on line 49 you will get the name from getColumnName. This works perfectly if your domainmodel exactly meets the database model. But in many cases the name of the attributes are different or the case is not equal. This results in a horrifying Null pointer exception. In your queries you want to use the AS statement eq. SELECT name AS FirstName FROM employees. If you want to change this you have to alter the ResultSetIterator on row 49 from: columnName = resultSet.getMetaData().getColumnName(index); to columnName = resultSet.getMetaData().getColumnLabel(index); Kind regards.