ReportServer 4.6.0 adds Incorta support, but as I mentioned, the error you got is not reproducible.
Here the release notes: https://reportserver.net/releasenotes/RS4.6.0.html
Regards,
Eduardo
in your error stack I see many entries containing:
net.sf.jsqlparser
This is *not* included in reportserver. You seem to have additional libraries other than the shipped ones. This is probably the cause of the error.
Using the official Postgres driver (shipped with ReportServer) I don't get any errors with Incorta.
Pls double check your additional libraries (in the external config dir) and also in web-inf/lib (these should not be modified!)
Regards,
Eduardo
we tested ReportServer (4.5.0) with Incorta (in the cloud) and everything works as expected, no error. Maybe the newer Incorta versions allow the same configuration ? Can you pls check ?
Are you using Incorta on the Cloud? Maybe you use an older version.
My connection URL is similar to:
jdbc:postgresql://incorta-4439.sqli.cloud4.incorta.com:9603/default
Anyway, ReportServer 4.6.0 will probably include Incorta support, but as I mentioned, the error you got is not reproducible.
Regards,
Eduardo
a conference call would not help in this case. For the moment we don't have an incorta database, and in order to (eventually) support it, we would need to test it of course.
Regards,
Eduardo
the same here:
if you have any possibility of letting us access your (test)-incorta database (we just need to connect to a simple test table, e.g. "select * from mytable"), we can also take a look at this, as this seems interesting.
Regards,
Eduardo
Did you manage to get it to work by any means?
Regards Gerard
]]>i think there are available dummy environments in their free online courses: https://learn.incorta.com/
i took a look at the classes net.datenwerke.rs.base.service.dbhelper.db.PostgreSQL but did not found how to avoid this
SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
maybe something related to the line @Transactional(rollbackOn = { Exception.class }),
in TableReportUtility, datasourcetester and other classes
dont know
regards
]]>if you have any possibility of letting us access your (test)-incorta database (we just need to connect to a simple test table, e.g. "select * from mytable"), we can also take a look at this, as this seems interesting.
Regards,
Eduardo
pls take a look here:
https://reportserver.net/en/guides/scri … tasources/
You can try to add this datasource type via script. It this works you can send us the script and we will consider integrating this into ReportServer.
Pls. let us now.
As the only issue seem to be the statements added, this should not be very difficult if you base on the Postgres database helper:net.datenwerke.rs.base.service.dbhelper.db.PostgreSQL
https://reportserver.net/api/current/ja … reSQL.html
Regards,
Eduardo
or maybe there is a way of using the current postgres one adding some kind of hook to avoid non select statements added by the current ?
kind regards
]]>and the server to connect uses:
https://docs.incorta.com/5.1/concepts-sqli/
it supports select queries via postgres jdbc
thanks
]]>what reportserver version exactly are you using and what postgres version?
Regards,
Eduardo
that part of the error stack is provided by the server response, the incorta server response when reportserver opens the connection.
it does not seem to support the query that RS adds SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
as i told you there are no problems connecting via jdbc on birt, or via script reports using jdbc in groovy.
but we need to connect also in dynamic lists, and the data source connection fails.
is there any property we could indicate RS not to send that unsolicited query/instruction?
or maybe RS developers could provide another postgres datasource type, one did not add up additional non select queries
kind regards
]]>jsqlparser ? this seems to not be included in a standard reportserver installation, did you add any libraries / drivers regarding your postgres database ?
Regards,
Eduardo