forked from tora-tool/tora
/
ISSUES
134 lines (91 loc) · 5.65 KB
/
ISSUES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
Showstopper Issues before Next Release
--------------------------------------
Minimize sf.net error backlog - bugtracker.
Walk through basic tasks and dialogs and test its functionality. (create table, drop, alter etc.)
Minor Issues that would be nice to fix before release
-----------------------------------------------------
[Nathan] Proper encoding of author names in about dialog.
Enhancements
------------
[needs work] Would love it if the Schema Browser/connection would remember the
last schema that was being browsed. In our environment, the user you connect
as never owns any objects, so if I connect as 'swconf', I'll almost always
be browing 'swconf_owner' schema. - This has some overlap with the next suggestion.
[needs work] Would be nice to be able to specify/store a default schema with the db
connection.
[IGNORE/FUTURE] Create table/create index isn't working in the Schema Browser.
[IGNORE/FUTURE] MIGRATE extraction doesn't work (and I suppose it never did)
Resolved Issues
---------------
[FIXED- PV] Edit Sql and Chart Manager menu options enter infinite loop. These did
work but may have been broken since the QMdiArea change.
[working?] Oracle: better handling on extents tab if no access to dba_extents view.
[PARTIALLY FIXED - Petr - there is no clear() method for toResult(). So you can get an error message "foo doesn't exist" in some schema changes (Data tab). All other tabs should work fine. Content is cleared in all cases. ]
[PARTIALLY FIXED - resolved the error message, but column list still doesn't get cleared]
When switching in schema browser from looking at columns of a table to a schema with no tables, the column list never gets
cleared. It stays as the column list from the original table.
[RESOLVED] Row number in first column of schema browser for 'Data' tab - needs to resize to fit contents - right now, it truncates.
Drag and drop in schema browser to copy table cells.
[can't be done] ">|" arrow on schema browser view just scrolls to bottom of display instead of reading all rows as it used to.
Drag and drop/doubleclick in filter dialog for schema browser no longer works.
[MOSTLY WORKED AROUND - no perms to tables] Oracle: error "result should be 18 in segment attributes was 2" in toExtract on Script tab
[i don't get this error, can you send a table create script that'll reproduce?]
[FIXED] - petr
CRASH - fix crash in the DB Extract tool on "Search" and/or "Compare" feature.
It looks like there is an infinite loop somewhere.
...
#100 0x0844d4c1 in toResultViewCheck::allText (this=0x8cb34f8, col=0)
at /home/subzero/tora/trunk/src/toresultview.h:420
#101 0x0844d526 in toResultViewMLCheck::text (this=0x8cb34f8, col=0) at /home/subzero/tora/trunk/src/toresultview.h:487
#102 0x0844d4c1 in toResultViewCheck::allText (this=0x8cb34f8, col=0)
at /home/subzero/tora/trunk/src/toresultview.h:420
etc. etc.
[FIXED] - petr
DB Export doesn't work... Not as concerned about the compare part.
Clicking on either of the "sql bookmark" toolbar icons instantly crashes tora.
[not fixing. i think you mean:
create table foo (bar varchar2(10));
begin
insert into foo values ('sasa');
end;
select * from foo;
]
Batch(script) run in SQL Editor. See:
http://sourceforge.net/mailarchive/forum.php?thread_name=e50db5a5f5be244c6ad03556ffd7fa76%40office.scribus.info&forum_name=tora-develop
Regulary raising warning/error dialog with:
ORA-24374: define not done before fetch or execute and fetch
<ERROR>SELECT TO_CHAR(SYSDATE) FROM sys.DUAL
propably used as "keep session alive" (?)
MySQL: Lots of "database not open" warning msgs
MySQL: numerous crashes in schema browser - running under gdb hides a lot of these unfortunately... has been stable
[DONE in revision #2812?] Stray/unecessary "save changes to editor" dialogs that don't make much sense or no modified data.
Double click in schema browser causes it to interpret as 'changed' even
if no changes are made.
[hit escape?]
[FIXED] Explain Plan shortcut prints to stdout:
QAction::eventFilter: Ambiguous shortcut overload: F3
- explain plan mode uses F6 now. F3 (search next) is working again.
[Mike] Storage manager functionality
[DONE - some issues can be found by testing of course] [Petr] Completion of conversion to use QSettings
[FIXED] Seems like there is an extra column in the connection dialog, looks
weird.
[FIXED] New prefs code not saving anything? Showing dialog every time TOra opens
and not retaining default tool.
[good enough] 11g compatibility
- mostly works fine but should have a compile option
(not use 10g). several sql queries need to be tweeked, tora locks up
when cache runs.
[probably unrelated noblock crash that should be fixed by toeventquery]
Crash if you click trashcan/delete-row on empty table in schema browser
[mrj: can't reproduce this, can you send me a stacktrace? the code
does the right thing it appears.] [nneul: nor can I now... weird... will
leave this in for a little bit, if it returns, I'll get you a trace]
[RESOLVED] Single clicking in sql editor entry area if entire text is selected causes
the selected text to be pasted at the end of the entry area as if you
middle-clicked. Picture normal behavior of selecting it all to copy it, then
single clicking to unselect it and move to something else...
[FIXED - is it suitable?] "Waiting..." shows up in right pane in schema browser
until you click on a table name also stays up if no tables in schema.
[RESOLVED - see toMessage class and its comments - I faced a real DoS flooding by this dialog today - Petr]
Error warning dialogs are modal, and have to be closed in the right order. Ideally - would like to see the error popups
be a single window, something in the style of the javascript error console in firefox perhaps?