-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Tue, 22 Jan 2002 11:50:37 +0100 Source: sql-editor Binary: sql-editor Architecture: source all Version: 0.1 Distribution: unstable Urgency: low Maintainer: Andrea Mennucc <debian@tonelli.sns.it> Changed-By: Andrea Mennucc <debian@Tonelli.sns.it> Description: sql-editor - editor of SQL databases, with 'join' capability Changes: 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 Files: 5dff1cd55a752165ddb3e705d1a453c7 547 editors optional sql-editor_0.1.dsc 626ec57eb52c71815cff33d6a8c64ecf 15650 editors optional sql-editor_0.1.tar.gz ccc149d7dab6d3e62e37cd66329abbf5 17678 editors optional sql-editor_0.1_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8UARF9B/tjjP8QKQRAtybAJ9XH3i+HGxtzxRybv8QGPbZlL/7ZACffeQx 8ZBv3luVX5kl4P9ijB9V3nw= =14wE -----END PGP SIGNATURE----- Installed: sql-editor_0.1.dsc to pool/main/s/sql-editor/sql-editor_0.1.dsc sql-editor_0.1.tar.gz to pool/main/s/sql-editor/sql-editor_0.1.tar.gz sql-editor_0.1_all.deb to pool/main/s/sql-editor/sql-editor_0.1_all.deb