Re: [metabase-dev] pearifying metabase: phase 1

Hello, Lukas Smith wrote: > > > > - DSN support (minor) > > > > This was planned to be added to Metabase similarly to JDBC and it > seems > > to PEAR-DB. I just disagree that the database name be required in the > > DSN as it seems that PEAR-DB requires. Metabase lets you change the > > database to each you want to connect in the with the same driver > object > > instance. Actually you may perform queries to a server that has no > > databases installed. So what PEAR-DB does? I haven't checked, but does > > it fails to connect because you did not specify a database name? > > so I will not worry about doing this myself for now Yes, it is basically calling parse_url and assigning the result values to arguments array of MetabaseSetupDatabase. > > > - tableInfo (minor: metabase allready has some of those features) > > > > Actually Metabase does not have this yet. I want to add it because I > > want Metabase manager to be able to reverse engineer schemas of > > applications already installed by traditional means, to encourage > people > > to migrate to Metabase and use the database independent schema > > definition. > > Well you can get the column names in metabase iirc. Yes, that is for result set metadata not for table metadata. > But if you are working on this I will also not worry about this for now. Yes, but it will not be ready soon at least upto the level I want it which is to reverse engineer schemas installed by traditional methods. I need to give some thought about how to resolve data type mapping ambiguities. Regards, Manuel Lemos