Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Cannot load from postgresql database into writer (ODBC) | ||
---|---|---|---|
Product: | Writer | Reporter: | climac <clive.maclean> |
Component: | ui | Assignee: | Oliver Specht <os_ooo> |
Status: | CLOSED FIXED | QA Contact: | issues@dba <issues> |
Severity: | Trivial | ||
Priority: | P2 | CC: | issues, stx123 |
Version: | 641 | Keywords: | oooqa |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux, all | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
climac
2002-02-11 10:24:39 UTC
Hi, I can reproduced this problem. MSC -> FS: see trk id 98373 Ciao Marc changing the ownership to OS (Oliver Specht) - he is responsible for the dialog (dragging the rows into the writer doc triggers writer code) *** Issue 3760 has been marked as a duplicate of this issue. *** *** Issue 4609 has been marked as a duplicate of this issue. *** changing component - should have done this when transfering the ownership to OS Investigation of the problem has to be postponed due to heavy work load. Not a database/platform problem - the same problem exists with MySQL on both Linux and NT. A workround is to use the 'Data to Text...' button on the toolbar instead, which works correctly. This suggests there's nothing wrong with the underlying code - just the way it's invoked by 'drag and drop'. *** Issue 6091 has been marked as a duplicate of this issue. *** Oliver, I am sorry, but I have to re-open this issue. "Resolved Later" implies that nobody finds this issue when searching for it. We already have 3 duplicates of this issue, one where I could not convince the submitter that it is an duplicate (though I strongly believe so - issue 4811), and another one where I suppose that it is a duplicate, too (issue 5660). All of this shows me that the issue is of rather high importance, and thus I * re-open it (to allow people to find it) * change the priority to P2 (from P3) * add the keyword ODBC to the summary, as this is a common denominator of all know issues so far: It affects only ODBC. *** Issue 4142 has been marked as a duplicate of this issue. *** *** Issue 5660 has been marked as a duplicate of this issue. *** Hi Clive, will be fixed in the next OOo release (should also be in srx643 developer release). Best regards, Ocke certinly fixed in 644_m4. Thanks. I have installed version 1.0.2 and find that the fault is still present, in that if I select some records from the data window and drag them into the text document the 'insert database columns' window appears and when I select ok then the window disappears but nothing is added to the document. If instead of trying to drag the records I press the 'data to text' button in the toolbar the 'insert database columns' window appears and everything works fine. I am also able to drag the contents of a table field into the text ok. Clive, this bug was never targeted for 1.0.x - I change the target milestone to "1.1 Beta 2" now to point this out. The 1.0.x branch is intended for fixing serious bugs, and has high limitations in what is accepted for it, to keep the branch as stable as possible. Thus, this fix here won't make it into 1.0.x - sorry to say, but it's not "serious enough" (like a crash, or data loss, or something like this). Setting back to FIXED. Closed. |