Fixes in JDBC DatabaseMetaData #7126
Comments
|
Which orientDB version? Can you provide a snippet of code or better a test case that fails? |
|
Database and drivers 2.2.15, latest from the website.
On Thursday, January 26, 2017 6:02 PM, Roberto Franchini <notifications@github.com> wrote:
Which orientDB version?—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Ok, I guess you pass the resultSet and or the connection from one thread to another, e.g. from "backend thread" to the view. I'm improving this kind of use, I'll notify you when I've got something ready |
|
I've done some improvement on thread safety. You can download the latest 2.2.16-SNAPSHOT jar and try it instead of the 2.2.15 you have. |
|
Could you please paste here an URL to this file ? Not sure where to download it, thank you.
On Saturday, January 28, 2017 3:54 PM, Roberto Franchini <notifications@github.com> wrote:
I've done some improvement on thread safety. You can download the latest 2.2.16-SNAPSHOT jar and try it instead of the 2.2.15 you have.
I hope it could work fine. Let me know please—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
@dprutean did you have time to test the SNAPSHOT? |
|
We still get this error in one place, but generally looks better. Now we have problems when calling DatabaseMetaData.getTables(). Always got 'TABLE' where the table name should be.Please check also getColumns(), getIndexes(), getImportedKeys(), getExportedKeys()Based on this information we may build a diagram out of schema.We used this script in OrientDb: create class Person extends V;create property Person.birthday date;
create class Book extends V; create property Book.translation embeddedmap;
create class Relation extends E; create property Relation.from date;
create class Appear extends E; create property Appear.chapter embeddedlist integer
insert into Person (last, first, birthday) values ('Vimes', 'Samuel', '1962-04-03'); insert into Person (last, first, birthday) values ('Ramkin', 'Sybil', '1969-09-06');
insert into Book (name, translation) values ('Guards! Guards!', {'de':'Wachen! Wachen!', 'fr' : 'Au Guet!'} );
create edge Relation from #11:0 to #11:1 set type='Married', from='1993-01-01';
create edge Appear from #11:0 to #13:0 set chapter={1,2,3,4,5,6};
On Monday, January 30, 2017 10:45 AM, Roberto Franchini <notifications@github.com> wrote:
Here's a valid link: https://oss.sonatype.org/content/repositories/snapshots/com/orientechnologies/orientdb-jdbc/2.2.16-SNAPSHOT/orientdb-jdbc-2.2.16-20170130.172309-22-all.jar—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
which place? About the rest, I'll check all the calls. Note that some of these calls sometimes are hard to map to the inner OrientDB data model. I guess you had the same kind of problem with other noSQLs |
|
Could you share with me a snippet of code that shows errors and wrong metadata? |
|
hi, the new JDBC jar contains a fix for the table name: please test it and report here any problems. |
|
I just updated columns and indexes metadata mapping. |
|
For some reason I had to download again the latest version of OrientDb. Now I got an connection exception which I list below Few more remarks beside this:
com.orientechnologies.orient.enterprise.channel.binary.OResponseProcessingException: Exception during response processing |
|
Which versions are you using?
About demo database, we are working on a new demo db for 3.0.x, that is still in development. We don't know yet if the new demo db will be backported to 2.2.x |
We try to use the JDBC.DatabaseMetaData to discover database structure. For this we call getSchemas() getTables() getColumns() getIndexes(), etc.
After getSchemas() we receive an error 'The database instance is not set in the current thread'. Could you please set this directly in the JDBC driver ? Since we pass in the JDBC URL the database name, I think the driver should take care about it.
If we succeed to fix all this methods we will have a database design tool compatible with OrientDb ( the tool is dbschema.com ).
The text was updated successfully, but these errors were encountered: