driver should return columns for buckets

[j-larson]

When the current driver is used with DBeaver, it shows the tables but not not the columns within. This is because DatabaseMetaData.getColumns() returns an empty result set.

We could fix this by using INFER to deduce the de facto columns in each bucket.

This would also fix the problem that although indexes are shown in DBeaver when using our driver, index columns are not, though they are returned by our driver.

[keshavmr]

Hi Johan,

Yes. We should do this via INFER, but document the uncertainty of this result for the flexible schema.

Cheers, Keshav | 510.676.0824 | Bloghttp://www.planetnosql.com | @rkeshavmurthyhttps://twitter.com/rkeshavmurthy

From: Johan Larson <notifications@github.commailto:notifications@github.com>
Reply-To: jdbc-json/jdbc-cb <reply@reply.github.commailto:reply@reply.github.com>
Date: Friday, September 2, 2016 at 9:55 AM
To: jdbc-json/jdbc-cb <jdbc-cb@noreply.github.commailto:jdbc-cb@noreply.github.com>
Subject: [jdbc-json/jdbc-cb] driver should return columns for buckets (#54)

When the current driver is used with DBeaver, it shows the tables but not not the columns within. This is because DatabaseMetaData.getColumns() returns an empty result set.

We could fix this by using INFER to deduce the de facto columns in each bucket.

This would also fix the problem that although indexes are shown in DBeaver when using our driver, index columns are not, though they are returned by our driver.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/54, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKOG8M9awLHEvVVYSsEU8C3tG-0Cmyr5ks5qmFUWgaJpZM4Jz5Yh.