Bugzilla – Full Text Bug Listing
| Summary: | DataSource Explorer doesn't show Schema | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] Data Tools | Reporter: | Michael Woski <woskimi> | ||||
| Component: | Data Source Explorer | Assignee: | Project Inbox <dtp.enablement-inbox> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | m.hoffmann, rodrigoaraujoeti | ||||
| Version: | 1.5 | Keywords: | helpwanted | ||||
| Target Milestone: | 1.6 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Michael Woski
Michael: I tried this in the DTP 1.5 4/9 and couldn't repro. Connected to PostgreSQL 8.1.2, DSE tree OK, close connection, relaunch Eclipse, connect, and everything's still fine. Next, tried connecting to PostgreSQL 8.1.2, DSE tree OK, close Eclipse without closing connection, relaunch, connect, DSE tree still OK. Could you provide some more details about the DB that you are connecting to, your OS, and so on? Thanks Hey John, My guess is that this is a problem with the way the connection profile is configured. If an extender fails to include the database vendor and version properties, the ConnectionInfoImpl can't find the DB definition, which is probably what is causing this error. Not sure why it works once. Just a guess. Rob Hi John, I'm using a MySQL 5.1 database. I tried both the recent 3.1.14 and 5.0.5 JDBC connectors with the standard Driver class. It's all the same, I even tried a fresh workspace just to be sure.. The Drivers are configured under MySQL 4.1 (whatever that 4.1 means) in the Connectivity Preferences. When the problem shows and I change the driver from the drop down list in the JDBC Connection Properties (Data Source Explorer -> Database -> Properties) everything's fine again (including connecting/disconnecting/reconnecting) - until the next restart of Eclipse. The other thing I should also mention is, I'm using the M6 Eclipse build on Linux/GTK2(x86_64). Hi John, there's news here. I tried the same thing with a PostgreSQL database and it worked like a charm, as long as the new Connection Profile had been chosen from the "PostgreSQL JDBC Connection". However, as soon as you create a new connection from an "SQL Model JDBC Connection", either to a MySQL or a PostgreSQL database, things mess up like previously mentioned; note, it does so with every(!) profile, even those that used to work before the addition of the "SQL Model JDBC Connection". Deleting the latter does not solve the problem with the other profiles though, in the sequel they still show that corrupted behaviour. Hope I could help Michael: When DTP 1.5RC0 is available (target: 5/11), please retest this for MySQL. I saw the same problems, but they appear to be fixed with the recent updates of the MySQL driver templates and db definition files. (In reply to comment #5) Hallo John, unfortunately RC0 didn't fix things, however, it changed them. Despite showing only the catalog given in the URL of the connection profile, one can actually see all those that are available in the database. For each of those catalogs the next thing to see is the "Schemas" folder, but with nothing in it. Also, no exceptions are thrown anymore. It still applies that when the connection profile is new it works just fine, until you restart eclipse. Hey Michael, Could you please provide a set of detailed steps to reproduce this problem? Thanks in advance, Rob Hey Rob, it's quite simple. I create a new Connection Profile, one time with a MySQL server and the other time I do the exact same thing with a PostgreSQL server. In the latter case everything works as you would expect, in the first case it does so too but only as long as you don't close and reopen eclipse. It really is just an issue with MySQL, or let's say it doesn't happen with PostgreSQL. To clearify what the problem looks like on the screen I'll attach a little file. bye M;chi Created attachment 67274 [details]
View of Data Source Explorer
for the first connection the "amarok" schema had been specified in the connection URL, but instead I get a complete list with nothing in it though.
For postgres it just works, as you can see
Will continue to look at this post 1.5. Might need Enablement support for MySQL... (In reply to comment #10) Hello, I encountered this problem too with MySQL. The problem always appears if i have unchecked save password in the connection profile. So I have to click to connect, give the password and after that I see the connection described before with catalog and schema but no tables. Editing the connection profile doesn't help in my case, so I have to recreate the profile and check save password and everything is fine. Mark Is this still an issue with Ganymede? (In reply to comment #12) > Is this still an issue with Ganymede? Hi, it now works properly, at least for me. thx for all the effort NP. Resolving as fixed. Closing bug Im using db2. In localhost it works fine, but remote don't. |