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
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
|
sql-editor (0.17) unstable; urgency=low
* update to python policy
* update standards
* correct man section
* quoted menu strings
* disable Postgres support (never worked anyway)
-- A Mennucc1 <mennucc1@debian.org> Tue, 15 Aug 2006 10:34:31 +0200
sql-editor (0.16) unstable; urgency=low
* skip last char when pasting forms into select entries
* fast-selection-entries should return NULL and not 0 if unset
* convert tab in spaces when pasting forms into entries
* convert tab into % when pasting forms into select entries
* reset clears all select values
* the NMU version did not even start on my box!
* unfortunately the upload of this version was lost, reuploading
-- A Mennucc1 <mennucc1@debian.org> Sat, 22 Nov 2003 10:13:45 +0100
sql-editor (0.15) unstable; urgency=low
* NMU.
* Update depends for pygtk transition (closes: #208129).
-- Matthias Klose <doko@debian.org> Thu, 25 Sep 2003 20:58:59 +0200
sql-editor (0.14) unstable; urgency=low
* values in the classes were not initialized at every instantiation:
so , if multiple windows were opened and closed, it was a mess
-- A Mennucc1 <mennucc1@debian.org> Fri, 29 May 2003 18:55:35 +0200
sql-editor (0.13) unstable; urgency=low
* now it can search into joins !
-- A Mennucc1 <mennucc1@debian.org> Fri, 9 May 2003 18:55:35 +0200
sql-editor (0.12) unstable; urgency=low
* bug: it was impossible to insert
* changed all print into logs
-- A Mennucc1 <mennucc1@debian.org> Mon, 5 May 2003 10:19:12 +0200
sql-editor (0.11) unstable; urgency=low
* always use text entries for text (GtkEntries go wild on ctrl chars)
* some aesthetix
* button to enlarge text entries as a popup window
* delete button to delete records
* complete rewrite of the logging system
* has sounds
* forced recompilation of python code (it sometimes failed to upgrade)
-- A Mennucc1 <mennucc1@debian.org> Tue, 30 Apr 2003 14:15:51 +0200
sql-editor (0.10) unstable; urgency=low
* data ordered by selection query
-- A Mennucc1 <mennucc1@debian.org> Wed, 23 Apr 2003 13:14:08 +0200
sql-editor (0.9) unstable; urgency=low
* user can choose the selection query
-- A Mennucc1 <mennucc1@debian.org> Fri, 21 Mar 2003 16:45:58 +0100
sql-editor (0.8) unstable; urgency=low
* paste forms from clipboard
-- A Mennucc1 <mennucc1@debian.org> Tue, 4 Mar 2003 13:41:39 +0100
sql-editor (0.7) unstable; urgency=low
* transition to gtk2 thanks Sebastien Bacher
* form read and write
* reads ~/.my.cnf
* date and datetime have calendar support
* text entries resize automatically
* corrected bug: last entry was never editable!
-- A Mennucc1 <mennucc1@debian.org> Mon, 24 Feb 2003 13:12:50 +0100
sql-editor (0.6) unstable; urgency=low
* calls 'import gtk' only where needed
-- Andrea Mennucc <debian@Tonelli.sns.it> Fri, 26 Apr 2002 11:27:35 +0200
sql-editor (0.5) unstable; urgency=low
* Dep: mysql | pgsql; if the user tries the one missing, s/he gets an error
* 'New' button (which is just 'reset' followed by 'edit')
* check some values before using them!
-- Andrea Mennucc <debian@Tonelli.sns.it> Thu, 11 Apr 2002 11:46:45 +0200
sql-editor (0.4) unstable; urgency=low
* relax dependencies on python-pgsql (closes: #138879)
-- Andrea Mennucc <debian@Tonelli.sns.it> Wed, 20 Mar 2002 12:01:27 +0100
sql-editor (0.3) unstable; urgency=low
* stupid workaround for "cant update" bug
* reformatted description (closes: #135311)
-- Andrea Mennucc <debian@Tonelli.sns.it> Wed, 6 Mar 2002 13:07:08 +0100
sql-editor (0.2) unstable; urgency=low
* sometimes the call database_connection.cursor()
returns None... then we log an error
-- Andrea Mennucc <debian@Tonelli.sns.it> Thu, 14 Feb 2002 15:22:31 +0100
sql-editor (0.1) unstable; urgency=low
* Initial Release.
Known Issues:
PostgreSQL support was never (NEVER) tested.
There is a problem in my understanding of python db api, or maybe
in the api itself; it is unclear how data are formatted by the call
cursor.execute("UPDATE table SET date=%s,... WHERE date=% &&..", (x,y) )
how do the dbAPi know that x should be
converted to timestamp or to a date, etc etc
Sometimes it is impossible to 'update'
datetime, time, timestamp... are not very well supported in general
I don't know how the program will behave when it encounters sets and blobs
text entries let the user enter more data than can actually fit in
the database field
it is not possible now to edit fields that are PRIMARY ; I don't know
what is the right thing to do... should they be editable or not?
maybe the answer is not general, but specific to the table
-- Andrea Mennucc <debian@Tonelli.sns.it> Tue, 22 Jan 2002 11:50:37 +0100
|
