|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Seeking improvements in Database Access | ||
|---|---|---|---|
| Product: | Base | Reporter: | jhansonxi <jhansonxi> |
| Component: | code | Assignee: | marc.neumann |
| Status: | CLOSED NOT_AN_OOO_ISSUE | QA Contact: | issues@dba <issues> |
| Severity: | Trivial | ||
| Priority: | P4 | CC: | issues |
| Version: | OOo 1.0.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
| Developer Difficulty: | --- | ||
|
Description
jhansonxi
2003-03-19 18:11:10 UTC
Just noticed that #8 is similar to Issue #11154 Jeff, thanks for the feedback on this. Lemme first comment the single items: > 1. The table view in the Data Source Browser doesn't seem to pick > an optimal width very well. Fields often waste space or are cut off > by the next column. What is "optimal"? The current behaviour is that columns are resized according to the column title, while you can resize it (with a double click onto the header) to the content of the (visible) fields in this column. I currently cannot imagine any good heuristic which fits _much_ better. Can you suggest one? > The table view makes poor use of the available window width. How so? > 2. The Data Source Browser should remember manually adjusted > columns sizes. It is intended to do. If it doesn't (in my environment, it _does_), please try to come up with a concrete scenario, and file a bug for this. > 3. It should be possible to change column order by dragging > headers; Yes :) I simply agree here, this is on our list for quite some time, but not on a very high rank, admittedly. > 4. It would be easier to adjust record view order by clicking on > column headers to change between ascending/descending sort order. It is intentionally _not_ implemented this way. The reason is that sorting means a roundtrip to the server, which is potentially expensive (sometimes _very_ expensive), so we did not want to allow this to be done by such a simply action which often is done accidentially. However, it may be possible to enable such a behaviour optionally. > 5. Rows dragged from the DSB (Database Ranges) to the spreadsheet > always include the field names This is a separate Calc issue which I cannot really comment about, due to lack of knowledge about Calc. > 6. Columns cannot be dragged from the DSB Columns themself _can_, but I suppose you mean a row selected, restricted to specific columns (as currently _all_ columns are included when dragging rows). Is this correct? If not, I do not get you, sorry. > 7. Need the ability to refresh a DSB import in Calc ... Same as 5. > 9. There should be an option in the DSB to allow field data longer > than the column width to wrap (Line Break). Not sure how the line height should be handled then. Adjusting it to the text could mean that you would have rows which take up the whole screen, which doesn't make sense to me. Not adjusting it means that the line break doesn't make much sense. I would agree that _entering_ the data in a multi-line-able field would make sense, but I am sceptic about displaying it as multi-line. > 10. There doesn't seem to be any way to get data from a spreadsheet > to a table except by dragging one cell at a time. It would be much > easier to input legacy data by being able to drag a cell range to an > existing table. Agreed. I would like _all_ tables in OOo (writer tables, Calc tables, Base tables, and the tables for the chart data input) to interoperate much better - I don't see any valid reason for the current bad interoperability. After jumping into the discussion with this, I would nevertheless strongly ask you to submit seperate issues for all of these - they are not really related, and if we address them, then certainly not all at once, so it does not make sense to have _one_ issue for _all_ of them. So could you please just file new enhancements? > So could you please just file new enhancements?
s/enhancements/enhancement requests/
1. I didn't know about double-clicking the column header. New Issue# 12524 2. I did some more checking and you are correct. It does remember the width for tables. But not for queries even if the title is clicked to fit the data width. As soon as I switch to a different query or table then back again, it is set to fit the column title only. New Issue# 12520 3. I can only hope. New Issue# 12521 4. Should not be an issue for a data source connected locally through ODBC. I was thinking that the sort was done locally and didn't affect the server. New Issue# 12522 5. I wasn't sure where the boundary was between the DSB and Calc. I'll post a new feature request under the specific app. New Issue# 12523 6. When I click on a column title (seleting the data in that column in all records) and drag it to Calc I get a control, not a columnar list of data copied from the records. In Writer, I get "<column title>" only. Not very intuitive. If I drag a row/record, I get the entire record and all column titles in Calc even if I don't want the titles (#5). In Writer at least, the Insert Database Columns (pilot?) dialog box allows me to not import the titles. It sounds like this is another one for the Calc or Writer teams. New Issue# 12518 and Issue# 12519 7. New Issue# 12525 and Issue# 12526 8. New Issue# 12527 9. New Issue# 12524 10. New Issue# 12528 Hi, So we can close this issue. Bye Marc . change subcomponent to 'none' Created attachment 73910 |