JDBC Compliance

The DATABASICS JDBC Driver supports querying data ONLY.

We do not support UPDATE, INSERT or DELETE

Know Limitations

Virtual Fields

Virtual fields are fields that are not physically present in the database but are created and added to the API response.

For instance, in the Employee table, we have two fields nFirst and nLast. However, in the API response, we also include the fullName field, which is created by combining the values of nFirst and nLast. Since virtual fields are created dynamically, they cannot be used to apply filters.

Select * from Employee where fullName = ‘john doe’

The above cannot be done since the fullName is a virtual field.

Joins with matching column names

We offer support for only inner joins in JDBC, meaning we cannot perform other types of joins. Additionally, when displaying the output of an inner join, we will only show columns with unique names. If there are columns with duplicated names, we will only display information from the first table involved in the join. See JOIN Queries for more information.

Camel Case

Our JDBC uses a camel case structure for the table columns. This is why at the actual database you will see EMPLY_ID while at the JDBC the same column is emplyID.

The same rule applies when creating an alias for columns, which means we cannot ever use the '_' in an alias name

Example :

Select firstName As NAME_FIRST
from Employee

The above example will not work because behind the scenes the NAME_FIRST is converted to nameFirst.

Page Size

The default pageSize from Admin for any list is 20 records. When a user selects data from the JDBC the backend will call the API until all data is fulfilled.

Query: SELECT * FROM Currency

Currency table contains 100 records

0……19 ← call 1

20…39 ← call 2

40…59 ← call 3

60…79 ← call 4

80…99 ← call 5