According to Erel's recommendation this SQL query should not be used with jRDC (dynamic queries) to avoid the chance of SQL injection
SELECT EmployeeName, ID FROM EMPLOYEES WHERE ID = 101
I want to make a query builder to compose SQL query statement to filter data before being populated to B4Xtable.
my idea is to pass 3 parameters to SQL stored procedure via B4J jRDC server
1- Table alias name (table1)
2- List of fields (EmployeeName,ID)
3- Conditions (ID = 101)
the stored procedure will lookup the table alias name (table1) to get real table name(EMPLOYEES ) and rebuild the SQL statement on SERVER using these 3 parameters, then execute it and send result back to application. The composed Select statement is not sent back to application.
is it safe to use this method or there is a better one?
TIA
SELECT EmployeeName, ID FROM EMPLOYEES WHERE ID = 101
I want to make a query builder to compose SQL query statement to filter data before being populated to B4Xtable.
my idea is to pass 3 parameters to SQL stored procedure via B4J jRDC server
1- Table alias name (table1)
2- List of fields (EmployeeName,ID)
3- Conditions (ID = 101)
the stored procedure will lookup the table alias name (table1) to get real table name(EMPLOYEES ) and rebuild the SQL statement on SERVER using these 3 parameters, then execute it and send result back to application. The composed Select statement is not sent back to application.
is it safe to use this method or there is a better one?
TIA