Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

Verify Datasource(s) #27

Open
MatsStromberg opened this issue Jan 30, 2013 · 1 comment
Open

Verify Datasource(s) #27

MatsStromberg opened this issue Jan 30, 2013 · 1 comment

Comments

@MatsStromberg
Copy link

The Verify of a datasource does not work any more... Nightlybuild after v2.0.2

No such function exists - cachedeleteall.

Request /bluedragon/administrator/settings/_controller.cfm

File Trace /opt/OpenBD/webapps/openbd/bluedragon/administrator/settings/_controller.cfm
|
+-- /opt/OpenBD/webapps/openbd/bluedragon/adminapi/Caching.cfc

@MatsStromberg
Copy link
Author

This issue still exist when it comes to verifying an Oracle Database. At the moment I don't have any other DB (like MySQL) setup to test if it's only hitting Oracle... But I suppose so.
Best Solution for target type Oracle would be to add a field for servicename (below the SID).
If this field would be filled should be using this rather than the SID.
dsinfo.servicename = ""; needs to be added to the _controller.cfm

driverManager = CreateObject("java", "java.sql.DriverManager")
I don't know how the DriverManager is able of handling this in the case of using a servicename rather than the SID. Normally the ojdbc will be using host:port/servicename rather than host:port:sid
I know too little about the DriverManager so maybe one simply need to use the normal OpenBD way to define the connectionwhen it comes to Oracle...

This also means that the bluedragon.xml will have an extra servicename field for an Oracle datasource, used or not..

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant