Is there any way to connect database without JDBC?

[kevin Liu]

Hi,

Any one has experience to connect to database without JDBC? I have a
project, and some application has conflict with JDBC. I have no
control on the application, but we still need to connect to database.
Could somebody help me?

Thank you so much.

Kevin

 

[Andrea Francia]

Hi,

Any one has experience to connect to database without JDBC? I have a
project, and some application has conflict with JDBC. I have no
control on the application, but we still need to connect to database.

Which DBMS you need to support?

 

[Donkey Hottie]

Hi,

Any one has experience to connect to database without JDBC? I have a
project, and some application has conflict with JDBC. I have no
control on the application, but we still need to connect to database.
Could somebody help me?

Thank you so much.

Kevin

What kind of conflict it is?

You could always use JDBC-ODBC bridge, and so connect to the database via
ODBC.

If it is some application running within your JVM that conflicts with the
jdbc, that would be odd.

 

[kevin Liu]

Which DBMS you need to support?

We use Oracle. Have any idea?

Thanks,

 

[Markus Tazl]

We use Oracle. Have any idea?

Thanks,

What kind of conflict, could you describe this more detailed ?

There are several ways to connect to Oracle beside JDBC (using C++ /
OCI for example)
but some more details on this particular problem might be helpful

regards
Markus Tazl

 

[softwarepearls_com]

Hi,

Any one has experience to connect to database without JDBC? I have a
project, and some application has conflict with JDBC. I have no
control on the application, but we still need to connect to database.
Could somebody help me?

Thank you so much.

Kevin

You'd be wise to try and resolve the JDBC issue, instead of trying to
circumvent it. If not, you're going down the slippery path of trading
something clean/simple/standard for something that is decidedly not.
Beware architectural rot ;-)

 

[kevin Liu]

What kind of conflict, could you describe this more detailed ?

There are several ways to connect to Oracle beside JDBC (using C++ /
OCI for example)
but some more details on this particular problem might be helpful

regards
Markus Tazl

I didn't see the actual error. We use IBM Rational product to do the
automation testing. It has conflict between the rational product and
JDBC when we connect database. IBM Rational sent some technical guys
to help us, but still cannot find any solutions. We are looking for
solutions other than JDBC to run the project. If you have any
suggestion, that will be wonderful.

Thanks for you time.

Kevin

 

[kevin Liu]

You'd be wise to try and resolve the JDBC issue, instead of trying to
circumvent it. If not, you're going down the slippery path of trading
something clean/simple/standard for something that is decidedly not.
Beware architectural rot ;-)

Thanks for your suggestion,

We will both at the time.

Kevin

 

[kevin Liu]

What kind of conflict it is?

You could always use JDBC-ODBC bridge, and so connect to the database via
ODBC.

If it is some application running within your JVM that conflicts with the
jdbc, that would be odd.

Thanks,

It's the problem what we have.....
Do you have any suggestion?

Regards,

Kevin

 

[Tom Anderson]

I didn't see the actual error. We use IBM Rational product to do the
automation testing. It has conflict between the rational product and
JDBC when we connect database. IBM Rational sent some technical guys to
help us, but still cannot find any solutions. We are looking for
solutions other than JDBC to run the project. If you have any
suggestion, that will be wonderful.

If there's a conflict between JDBC and Rational's product, then you will
need to drop one of them. Hint: it's not JDBC.

tom

 

[Arne Vajhøj]

You could always use JDBC-ODBC bridge, and so connect to the database via
ODBC.

I would only recommend that to people with masochistic
preferences ...

Arne

 

[Arne Vajhøj]

It's the problem what we have.....
Do you have any suggestion?

The problems should be solvable even if you need different
versions of the same JDBC driver you should be able to
accomplish it with clever usage of classloaders.

Arne

 

[Firefox 32]

I didn't see the actual error. We use IBM Rational product to do the
automation testing. It has conflict between the rational product and
JDBC when we connect database. IBM Rational sent some technical guys
to help us, but still cannot find any solutions. We are looking for
solutions other than JDBC to run the project. If you have any
suggestion, that will be wonderful.

Thanks for you time.

Kevin

Could the problem be related to a particular JDBC driver ? Conflicting
class name ?

Perhaps another driver might work without a problem, like JDBC-ODBC
bridge, or LDBC - universal (sort of) JDBC driver.

http://ldbc.sourceforge.net/

DG

 

[Firefox 32]

A conflicting class name is highly unlikely. A standard Java component
like a JDBC driver from a reputable source will use the
"inverted-domain" convention to name its classes, as in
"org.postgresql.Driver". Any other party would use a different package
hierarchy. If the OP is using a conflicting package hierarchy they
should stop doing that, but I doubt they are.

I meant that, perhaps, another version of the same jar is loaded in the
same time. Recently I have encontered that kind of a problem. One of two
companies cooperating had a tight deadline and failed to communicate
properly with the other.

DG

 

[Msj121]

I meant that, perhaps, another version of the same jar is loaded in the
same time. Recently I have encontered that kind of a problem. One of two
companies cooperating had a tight deadline and failed to communicate
properly with the other.

DG

Hmmmm, as others mentioned the problem is not really stated here.

Nonetheless, I am wondering - is the problem even in the connection
itself? Or can you connect but are unable to send/receive data etc....
It would be helpful to narrow down exactly what the issue might be.

 

[Arne Vajhøj]

A conflicting class name is highly unlikely. A standard Java component
like a JDBC driver from a reputable source will use the
"inverted-domain" convention to name its classes, as in
"org.postgresql.Driver". Any other party would use a different package
hierarchy.

It happen all the time.

The problem is two different versions of the same code.

Arne

 

[Arne Vajhøj]

I meant that, perhaps, another version of the same jar is loaded in the
same time. Recently I have encontered that kind of a problem. One of two
companies cooperating had a tight deadline and failed to communicate
properly with the other.

It happens all the time.

Luckily it is usually not a problem because in a Java EE context
you usually already have multiple classloaders in place to handle it.

Arne

 

[Arne Vajhøj]

Could the problem be related to a particular JDBC driver ? Conflicting
class name ?

Perhaps another driver might work without a problem, like JDBC-ODBC
bridge, or LDBC - universal (sort of) JDBC driver.

http://ldbc.sourceforge.net/

Since LDBC will use the real JDBC driver, then it is far from
obvious that it will solve the problem.

Arne

 

[Firefox 32]

Since LDBC will use the real JDBC driver, then it is far from
obvious that it will solve the problem.

Looks like I've misunderstood LDBC.

DG

 

[Firefox 32]

Hmmmm, as others mentioned the problem is not really stated here.

Nonetheless, I am wondering - is the problem even in the connection
itself? Or can you connect but are unable to send/receive data etc....
It would be helpful to narrow down exactly what the issue might be.

I am not familiar with the IBM product mentioned, don't know if it
includes any JDBC drivers itself. If it does, it might create a conflict.

DG