LucidDB / luciddb

DEFUNCT: See README
https://github.com/LucidDB/luciddb
Apache License 2.0
52 stars 24 forks source link

[FRG-89] !columns and !describe won't work on sys_fem."Config"."FarragoConfig" table #781

Open dynamobi-build opened 12 years ago

dynamobi-build commented 12 years ago

[reporter="kinkoi", created="Wed, 22 Mar 2006 12:43:16 -0500 (GMT-05:00)"] Here is the output

0: jdbc:farrago:> alter system set "calcVirtualMachine" = 'CALCVM_JAVA';
No rows affected (0.011 seconds)
0: jdbc:farrago:> !columns sys_fem."Config"."FarragoConfig";
+------------+--------------+-------------+--------------+------------+--------
+
| TABLE_CAT | TABLE_SCHEM | TABLE_NAME | COLUMN_NAME | DATA_TYPE | TYPE_N
|
+------------+--------------+-------------+--------------+------------+--------
+
+------------+--------------+-------------+--------------+------------+--------
+
0: jdbc:farrago:> !describe sys_fem."Config"."FarragoConfig";
+------------+--------------+-------------+--------------+------------+--------
+
| TABLE_CAT | TABLE_SCHEM | TABLE_NAME | COLUMN_NAME | DATA_TYPE | TYPE_N
|
+------------+--------------+-------------+--------------+------------+--------
+
+------------+--------------+-------------+--------------+------------+--------
+
------- Comment #1 From John Sichi 2004-07-16 12:25 [reply] -------
Right, Farrago doesn't currently have any metadata capability for virtual catalogs like sys_fem. This is not something planned for the near future so downgrading to P4.

dynamobi-build commented 12 years ago

[author="jhyde", created="Fri, 1 Aug 2008 01:37:02 -0500 (GMT-05:00)"] JVS wrote:


Fixing it requires


a) implementing method queryMetadata in
net.sf.farrago.namespace.mdr.MedMdrNameDirectory via MOF reflection
(similar to what is already done in there for instantiating row types
for direct references like sys_fem."SQL2003"."Schema"


and


b) figuring out how to copy the results of (a) into the catalog, e.g. by
something like IMPORT FOREIGN SCHEMA during catalog initsql (this is the
easiest way to make it queryable via JDBC metadata calls)