In version 1.12 of the table grid editor, we introduced the Datasource Specifications. You can configure datasources and use them in multiple grids.
The inner specifications are meant for backward compatibility.
The Table Grid Editor add-on uses the hibernate framework as underlying level for handling all database related connectivity. This approach gives possibility to use any database supported by Hibernate, as long as the required database drivers for that database are available for the add-on.
Current version of Table Grid Editor is delivered with several embedded jdbc database drivers for MySql, PostgreSQL, MS Sql Server and Oracle.
Following properties can be defined / used
|datasource.names||define the datasources in use in this grid. Further specified in [database detail|
|ds.xyz.connection.type = mysql||Use this to create a database source which connects to a mysql type of database.|
|ds.xyz.connection.type = oracle||Use this to create a database source which connects to an oracle database.|
|ds.xyz.connection.type = postgres||Use this to create a database source which connects to a postgres database.|
|ds.xyz.connection.type = sqlserver||Use this to create a database source which connects to a MS Sql Server type of database.|
|ds.xyz.connection.type = sybase||Use this to create a database source which connects to an sybase database.|
Also check the database reserved words. If you use this as a column name in your query, you will get a warning that this might collide with the underlying dml/ddl.
Check also connecting the grid to a database for some examples of how to configure the grid.
- Be very careful with the queries.
You might use a query which brings down the database instance, or use stored procedures which wipe the database.
- In certain cases, using the property gd.ds=jira in combination with SQL Server, will lock up JIRA.