search

ScriptMonkey00 / force-metadata-jdbc-driver

Automatically exported from code.google.com/p/force-metadata-jdbc-driver
0 stars 0 forks source link

JDBC issue #8

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Connect to Sales Force using the JDBC
2. You will be able to see the database structure but you can't see tables data
3. The issue comes from the implementation that is returning nulls:

JDBC driver issue: it is not fully implemented:

ResultSet rs = databaseMetaData.getProcedures(...) returns null

connection.createStatement() returns null

The standard JDBC metadata can be found here:

http://docs.oracle.com/javase/7/docs/api/java/sql/DatabaseMetaData.html

Original issue reported on code.google.com by donose.m...@gmail.com on 14 Nov 2013 at 8:56

GoogleCodeExporter commented 8 years ago 
Do you have a patch you would like included to address this? Presumably you are 
using this driver with some other tool than SchemaSpy?

Original comment by keith.cl...@gmail.com on 14 Nov 2013 at 9:24

GoogleCodeExporter commented 8 years ago 
I tried to use it with DbSchema, a database management tool.
Do you have a fix for it? or a procedure we can integrate so we can use the 
JDBC driver?

Original comment by donose.m...@gmail.com on 29 Nov 2013 at 9:20

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
In https://code.google.com/p/force-metadata-jdbc-driver/ you will see the 
opening statement that "This JDBC driver implements just enough of the 
java.sql.DatabaseMetaData interface to allow the wonderful SchemaSpy to output 
a set of ERDs for a Force.com data model".

So your choices are to implement the missing/wrong API yourself or use a 
product such as 
http://www.datadirect.com/products/datadirect-connect/jdbc-drivers/data-sources/
force-com where they have implemented the complete API.

Original comment by keith.clarke.claimvantage@gmail.com on 29 Nov 2013 at 9:40