Hello @billyb532 . Nice to see this old suggestion getting a bit of attention 🙂 I will try to address your points. SAS is not really my forte and I act as a middle man in this situation. Yes, we are aware it is a limitation. However, the essence of that suggestion was precisely to lift that limitation. Same goes for ODBC, ideally that limitation would be lifted on ODBC as well. Here's the anonymized code snippet we are using for our testing. I can confirm the issue is still happening %let jdbcstring= %NRSTR('jdbc:denodo://<host>:<port>/<db>?<jdbc options>');
libname mylib jdbc
classpath="<directory of jars>"
class="com.denodo.vdp.jdbc.Driver"
URL=&jdbcstring;
proc sql;
create table ttt as
select
cust.personal_id,
exp.balance_amt,
int.interest_rate_pctv
from
mylib.cust
inner join mylib.exp
on cust.fielda = exp.fielda
left join mylib.int
on exp.fieldb = int.fieldb
and exp.fieldc = int.fieldc
and int.fieldd = value
where
exp.fielde = value
and cust.fieldf = value;
quit; Unfortunately using DBMS views would not be an option in that case. We are using EG as a self-service tool precisely to prevent users from creating views in the DBMS Thank you for letting us know about the escape sequence hack, we will definitely look into that! Regarding connection properties, some JDBC drivers do not implement passing all possible connection parameters as URL, but instead force to pass it at the time of instantiation of the java Driver object. It is the case for some big DB vendors such as Vertica or MariaDB for example. The idea would be to be able to pass those instantiation parameters through the libname statement instead of the jdbc URL. I hope my answers helped you! Thanks again for looking into that.
... View more
