Hi Kasper, Yes, in fact we are using the JDBC module within our app. I was asking about the other way around, I thought you develop a first draft of it and it was not ready to use yet.
Kind regards, Alberto Alberto Rodríguez <http://www.stratio.com/> Vía de las Dos Castillas, 33, Ática 4, 3ª Planta. 28224 Pozuelo de Alarcón, Madrid Tel: +34 91 352 59 42 // *@stratiobd <https://twitter.com/StratioBD>* 2015-02-09 14:49 GMT+01:00 Kasper Sørensen <[email protected]>: > Hi Alberto, > > Well that's actually something quite different. We do have a JDBC module in > MetaModel which works fine - allowing you to use a relational/JDBC database > with MM. The module I think you're referring to is the other way around - > to expose a MetaModel DataContext as something that you can connect to with > JDBC. > > BR, > Kasper > > 2015-02-09 12:42 GMT+01:00 Alberto Rodriguez <[email protected]>: > > > Hi all, > > > > Kasper I thought that the JDBC MM driver was in a very early stage ¿? > > > > Kind regards, > > > > > > > > 2015-02-05 13:03 GMT+01:00 Kasper Sørensen < > [email protected] > > >: > > > > > Hi guys, > > > > > > On the DataCleaner forum we got some very nice feedback on a user's > > attempt > > > to connect to Apache Hive using MetaModel-JDBC [1]. > > > > > > To me it looks like that the "only" thing that's really going wrong is > > that > > > getIndexes() in JDBC does not work with their driver. I am thinking > that > > we > > > should maybe make our JDBC module fault tolerant in this call - maybe > > > databases cannot expose index information and their drivers therefore > > throw > > > an exception here. But that's IMO not really a blocker for MetaModel > > (just > > > a bit less metadata available). We should maybe then not throw any > > > exceptions? > > > > > > Kasper > > > > > > [1] http://datacleaner.org/topic/1044 > > > > > >
