crunchyfrog - Project Hosting on Google Code

Last 30 days Feb 21, 2010 issue 89 (AttributeError when using MySQL backend) reported by albrecht.andi - What steps will reproduce the problem? 1. Open SQL editor with MySQL connection 2. Hit TAB for autocompletion Traceback (most recent call last): File "/storage/devel/cf/default/cf/autocompletion.py", line 515, in on_editor_key_pressed_tab editor_autocomplete_advanced(editor) File "/storage/devel/cf/default/cf/autocompletion.py", line 129, in editor_autocomplete_advanced matches = get_matches(editor) File "/storage/devel/cf/default/cf/autocompletion.py", line 435, in get_matches completions = build_completions(editor, fragment) File "/storage/devel/cf/default/cf/autocompletion.py", line 311, in build_completions db.objects.Schema))] File "/storage/devel/cf/default/cf/db/objects.py", line 607, in get_full_name if hasattr(self, "schema") and not self.schema.is_default: AttributeError: 'Schema' object has no attribute 'is_default' What steps will reproduce the problem? 1. Open SQL editor with MySQL connection 2. Hit TAB for autocompletion Traceback (most recent call last): File "/storage/devel/cf/default/cf/autocompletion.py", line 515, in on_editor_key_pressed_tab editor_autocomplete_advanced(editor) File "/storage/devel/cf/default/cf/autocompletion.py", line 129, in editor_autocomplete_advanced matches = get_matches(editor) File "/storage/devel/cf/default/cf/autocompletion.py", line 435, in get_matches completions = build_completions(editor, fragment) File "/storage/devel/cf/default/cf/autocompletion.py", line 311, in build_completions db.objects.Schema))] File "/storage/devel/cf/default/cf/db/objects.py", line 607, in get_full_name if hasattr(self, "schema") and not self.schema.is_default: AttributeError: 'Schema' object has no attribute 'is_default' Earlier this year Feb 12, 2010 issue 81 (Display schema prefix?) commented on by halba1014 - hEY MOM WHATS UP SAND hEY MOM WHATS UP SAND Feb 02, 2010 issue 82 (Display/surface column information (pk, type etc)) commented on by albrecht.andi - That's great!! Take your time :) That's great!! Take your time :) Feb 02, 2010 issue 82 (Display/surface column information (pk, type etc)) commented on by darren.worrall - Hi, Sorry for the silence - I took a bit of a break over Christmas and have recently returned from holiday. I'll put a bit more work into a patch and get it over shortly. Thanks :) Hi, Sorry for the silence - I took a bit of a break over Christmas and have recently returned from holiday. I'll put a bit more work into a patch and get it over shortly. Thanks :) Jan 28, 2010 issue 88 (Executing lines with comment at the end fails) reported by albrecht.andi - What steps will reproduce the problem? 1. Try to run "select 1; -- a comment" 2. 3. What is the expected output? What do you see instead? The application sees the comment as a separate statement and tries to execute it, which leads to an error at least when using PostgreSQL. It should ignore the comment. Note, the application may behave different when the cursor is before or after the semicolon (F5, Shift-F5). Please use labels and text to provide additional information. What steps will reproduce the problem? 1. Try to run "select 1; -- a comment" 2. 3. What is the expected output? What do you see instead? The application sees the comment as a separate statement and tries to execute it, which leads to an error at least when using PostgreSQL. It should ignore the comment. Note, the application may behave different when the cursor is before or after the semicolon (F5, Shift-F5). Please use labels and text to provide additional information. Jan 27, 2010 issue 87 (Result can't be displayed when result set contains unhashabl...) changed by albrecht.andi - This issue was closed by revision 2fd6bbd1fe. Status: Fixed This issue was closed by revision 2fd6bbd1fe. Status: Fixed Jan 27, 2010 issue 85 (Some PostgreSQL error messages break markup.) changed by albrecht.andi - This issue was closed by revision 97afdb8537. Status: Fixed This issue was closed by revision 97afdb8537. Status: Fixed Jan 27, 2010 3 new revisions pushed by albrecht.andi - 97afdb8537:Properly escape errors messages (fixes issue85 ). e42cb8ea01:Update CHANGES. 2fd6bbd1fe:Don't use hashes when calculating best column width in results pane (fixes issue87 ). 97afdb8537:Properly escape errors messages (fixes issue85 ). e42cb8ea01:Update CHANGES. 2fd6bbd1fe:Don't use hashes when calculating best column width in results pane (fixes issue87 ). Jan 27, 2010 issue 87 (Result can't be displayed when result set contains unhashabl...) reported by albrecht.andi - What steps will reproduce the problem? 1. On PostgreSQL run: "select ARRAY[1, 2]" 2. 3. What is the expected output? What do you see instead? The result view should show the query results, but it fails silently instead: Traceback (most recent call last): File "/storage/devel/cf/default/cf/ui/editor.py", line 214, in on_query_finished self.results.set_query(query) File "/storage/devel/cf/default/cf/ui/editor.py", line 943, in set_query self.grid.set_query(query) File "/storage/devel/cf/default/cf/ui/editor.py", line 1053, in set_query self.query.coding_hint) File "/storage/devel/cf/default/cf/ui/widgets/grid.py", line 499, in set_result self._setup_columns(rows) File "/storage/devel/cf/default/cf/ui/widgets/grid.py", line 106, in _setup_columns samples = set(rows[:sample_size]) TypeError: unhashable type: 'list' Two things to fix here: 1) Internal errors should be reported in the UI; 2) That error shouldn't happen at all. Please use labels and text to provide additional information. What steps will reproduce the problem? 1. On PostgreSQL run: "select ARRAY[1, 2]" 2. 3. What is the expected output? What do you see instead? The result view should show the query results, but it fails silently instead: Traceback (most recent call last): File "/storage/devel/cf/default/cf/ui/editor.py", line 214, in on_query_finished self.results.set_query(query) File "/storage/devel/cf/default/cf/ui/editor.py", line 943, in set_query self.grid.set_query(query) File "/storage/devel/cf/default/cf/ui/editor.py", line 1053, in set_query self.query.coding_hint) File "/storage/devel/cf/default/cf/ui/widgets/grid.py", line 499, in set_result self._setup_columns(rows) File "/storage/devel/cf/default/cf/ui/widgets/grid.py", line 106, in _setup_columns samples = set(rows[:sample_size]) TypeError: unhashable type: 'list' Two things to fix here: 1) Internal errors should be reported in the UI; 2) That error shouldn't happen at all. Please use labels and text to provide additional information. Jan 20, 2010 issue 86 (setup.py build_mo fails when using sdist) reported by albrecht.andi - What steps will reproduce the problem? 1. Download (or create) source dist 2. Run "python setup.py build_mo" 3. What is the expected output? What do you see instead? Please use labels and text to provide additional information. What steps will reproduce the problem? 1. Download (or create) source dist 2. Run "python setup.py build_mo" 3. What is the expected output? What do you see instead? Please use labels and text to provide additional information. Jan 20, 2010 GettingStarted (How to download and run CrunchyFrog) Wiki page commented on by albrecht.andi - This will be fixed in the next release. Thanks for reporting! This will be fixed in the next release. Thanks for reporting! Jan 19, 2010 GettingStarted (How to download and run CrunchyFrog) Wiki page commented on by angelvelasquez - $ sudo python setup.py install running install running build running build_py running build_scripts running build_api running build_manpage running build_mo make: * No rule to make target `msg-compile'. Stop. Failed to compile message catalogs. $ sudo python setup.py install running install running build running build_py running build_scripts running build_api running build_manpage running build_mo make: * No rule to make target `msg-compile'. Stop. Failed to compile message catalogs. Jan 19, 2010 GettingStarted (How to download and run CrunchyFrog) Wiki page commented on by angelvelasquez - Sorry Andi, This tutorial isn't working :/ Sorry Andi, This tutorial isn't working :/ Jan 16, 2010 InstallingOnMacOS Wiki page deleted by albrecht.andi Jan 16, 2010 InstallingOnMacOs (How to install CrunchyFrog on MacOS) Wiki page added by albrecht.andi Jan 16, 2010 PreBuiltBinaries (How to install CrunchyFrog using pre-built binaries) Wiki page edited by albrecht.andi Jan 16, 2010 PreBuiltBinaries (How to install CrunchyFrog using pre-built binaries) Wiki page edited by albrecht.andi Jan 16, 2010 InstallingOnMacOS (How to install CrunchyFrog on MacOS) Wiki page added by albrecht.andi Jan 14, 2010 issue 85 (Some PostgreSQL error messages break markup.) reported by albrecht.andi - What steps will reproduce the problem? 1. Try to open a connection to PostgreSQL where the database was deleted. What is the expected output? What do you see instead? A error message should appear, telling what went wrong. Instead a dialog "Failed" appears. 1263465896.003036 ERROR __init__.py:246 Datasource.dbconnect failed: Traceback (most recent call last): File "/storage/devel/cf/default/cf/db/__init__.py", line 235, in dbconnect conn = self._open_connection() File "/storage/devel/cf/default/cf/db/__init__.py", line 215, in _open_connection conn = self.backend.get_connection(self.url) File "/storage/devel/cf/default/cf/db/backends/__init__.py", line 134, in get_connection conn = self.dbapi().connect(args, kwds) OperationalError: FATAL: Datenbank >>XXX<< existiert nicht /storage/devel/cf/default/cf/ui/dialogs.py:52: GtkWarning: Failed to set text from markup due to error parsing markup: Error on line 1 char 112: Odd character 'n', expected a '=' after attribute name 'existiert' of element '<' dlg.format_secondary_markup(long) Please use labels and text to provide additional information. What steps will reproduce the problem? 1. Try to open a connection to PostgreSQL where the database was deleted. What is the expected output? What do you see instead? A error message should appear, telling what went wrong. Instead a dialog "Failed" appears. 1263465896.003036 ERROR __init__.py:246 Datasource.dbconnect failed: Traceback (most recent call last): File "/storage/devel/cf/default/cf/db/__init__.py", line 235, in dbconnect conn = self._open_connection() File "/storage/devel/cf/default/cf/db/__init__.py", line 215, in _open_connection conn = self.backend.get_connection(self.url) File "/storage/devel/cf/default/cf/db/backends/__init__.py", line 134, in get_connection conn = self.dbapi().connect(args, *kwds) OperationalError: FATAL: Datenbank >>XXX<< existiert nicht /storage/devel/cf/default/cf/ui/dialogs.py:52: GtkWarning: Failed to set text from markup due to error parsing markup: Error on line 1 char 112: Odd character 'n', expected a '=' after attribute name 'existiert' of element '<' dlg.format_secondary_markup(long) Please use labels and text to provide additional information. Jan 11, 2010 issue 84 (patch to add export filter in Excel format) Status changed by albrecht.andi - Committed with a few minor changes re6677337e4 Thanks a lot! Status: Fixed Committed with a few minor changes re6677337e4 Thanks a lot! Status: Fixed Jan 11, 2010 Revision e6677337e4 (Add Excel export filter (fixes issue84, patch by Michele Alb...) pushed by albrecht.andi - Add Excel export filter (fixes issue84 , patch by Michele Albanese). Add Excel export filter (fixes issue84 , patch by Michele Albanese). Jan 11, 2010 Requirements (Requirements to run CrunchyFrog) Wiki page edited by albrecht.andi Jan 11, 2010 issue 84 (patch to add export filter in Excel format) changed by albrecht.andi - Status: Accepted Labels: Type-Enhancement Milestone-0.4.2 −Type-Defect Status: Accepted Labels: Type-Enhancement Milestone-0.4.2 −Type-Defect Jan 11, 2010 issue 84 (patch to add export filter in Excel format) reported by michele.albanese - Hello, I've implemented this export filter towards excel files. It requires the xlwt library as dependecy. Hello, I've implemented this export filter towards excel files. It requires the xlwt library as dependecy. Older Dec 23, 2009 issue 83 (Insert, Delete, Update functions in result pane) Status changed by albrecht.andi - This would only work if there's only one table affected by a SQL statement that populates the result pane. At least all selected columns need to be from the same table. Now that the SQL parser module used by the editor becomes more and more stable this feature should be possible. Status: Accepted This would only work if there's only one table affected by a SQL statement that populates the result pane. At least all selected columns need to be from the same table. Now that the SQL parser module used by the editor becomes more and more stable this feature should be possible. Status: Accepted Dec 23, 2009 issue 83 (Insert, Delete, Update functions in result pane) reported by giuseppe...@gmail.com - It will be nice to have Insert, Delete and Update functions in result pane like DataBrowser do. Compliments for the project! Best regards It will be nice to have Insert, Delete and Update functions in result pane like DataBrowser do. Compliments for the project! Best regards Dec 23, 2009 issue 82 (Display/surface column information (pk, type etc)) Status changed by albrecht.andi - Yepp, you're right. Detailed information about columns (and much more like views) are intentionally left out for now. But I like the first version (not the tooltip one). Would you mind to share your patch for it :) BTW, I thought of having some kind of detail pages opening in the main notebook (where the SQL editor lives). But that's a lot of work to do since it should be possible to display various kinds of objects (tables with colunms, constraints, ... or views with their definitions and so on). The hardest part is, once such objects are displayed you probably want to change them, e.g. renaming a column, adding a comment on a table or modify a view's definition. But something like that is definitely on the todo list :) Status: Accepted Yepp, you're right. Detailed information about columns (and much more like views) are intentionally left out for now. But I like the first version (not the tooltip one). Would you mind to share your patch for it :) BTW, I thought of having some kind of detail pages opening in the main notebook (where the SQL editor lives). But that's a lot of work to do since it should be possible to display various kinds of objects (tables with colunms, constraints, ... or views with their definitions and so on). The hardest part is, once such objects are displayed you probably want to change them, e.g. renaming a column, adding a comment on a table or modify a view's definition. But something like that is definitely on the todo list :) Status: Accepted Dec 17, 2009 issue 82 (Display/surface column information (pk, type etc)) reported by darren.worrall - I think it would be useful to display, or make available somehow more information on columns. It looks like you had this on your radar (looking at the __gproperties__ on objects.Column). How did you think it is best to surface the pk, type, default value and nullable information? One option would be to have a 'ColumnMeta' object and have it has a child to Column, and just expand it. I did a quick hack to show the data in a tooltip (attached). Part of thinks the column type should be very obvious - maybe by icon or as a string in brackets next to the column name? What are your thoughts on this? :) I think it would be useful to display, or make available somehow more information on columns. It looks like you had this on your radar (looking at the __gproperties__ on objects.Column). How did you think it is best to surface the pk, type, default value and nullable information? One option would be to have a 'ColumnMeta' object and have it has a child to Column, and just expand it. I did a quick hack to show the data in a tooltip (attached). Part of thinks the column type should be very obvious - maybe by icon or as a string in brackets next to the column name? What are your thoughts on this? :) Dec 15, 2009 issue 39 (stringobject.c:4491: bad argument to internal function) Status changed by albrecht.andi - Thanks :) I've just received feedback from the author of pymssql and it looks like this is fixed in pymssql 1.0.2. Status: Invalid Thanks :) I've just received feedback from the author of pymssql and it looks like this is fixed in pymssql 1.0.2. Status: Invalid Dec 15, 2009 issue 39 (stringobject.c:4491: bad argument to internal function) commented on by dunnomattic - Andi, That was it. The problem resolved after installing pymssql 1.0.2. Thank you (and thanks Darren). Of the many SQL clients I've ever used, crunchyfrog is my favorite by far...one client for Oracle/MySQL/SQL Server is so convenient. Like many others, I appreciate all of your effort. I have a few other questions for you that I'll take offline. -Matt Andi, That was it. The problem resolved after installing pymssql 1.0.2. Thank you (and thanks Darren). Of the many SQL clients I've ever used, crunchyfrog is my favorite by far...one client for Oracle/MySQL/SQL Server is so convenient. Like many others, I appreciate all of your effort. I have a few other questions for you that I'll take offline. -Matt Dec 15, 2009 issue 39 (stringobject.c:4491: bad argument to internal function) commented on by albrecht.andi - Thanks for investigating! I can't recall it, but I think I've seen a posting on some mailing list about a similar issue and it was related to the pymssql module. Today I've contacted the author of pymssql because the first item in the release notes for pymssql 1.0.2 looks much like this issue. I'll let you know when I've got a reply. Thanks for investigating! I can't recall it, but I think I've seen a posting on some mailing list about a similar issue and it was related to the pymssql module. Today I've contacted the author of pymssql because the first item in the release notes for pymssql 1.0.2 looks much like this issue. I'll let you know when I've got a reply. Dec 15, 2009 issue 39 (stringobject.c:4491: bad argument to internal function) commented on by dunnomattic - Albrecht - thanks for checking on this...it happens for any query, including each of the following ('applicant' is a table): select from applicant; select getdate(); SELECT SYSDATETIME(); Darren - I suspected it was something in like that in a dependent Python Python module. I'll see if I can find a version to pull. Thanks for the tip, I'll let you guys know what I see. Albrecht - thanks for checking on this...it happens for any query, including each of the following ('applicant' is a table): select * from applicant; select getdate(); SELECT SYSDATETIME(); Darren - I suspected it was something in like that in a dependent Python Python module. I'll see if I can find a version to pull. Thanks for the tip, I'll let you guys know what I see. Dec 15, 2009 issue 39 (stringobject.c:4491: bad argument to internal function) commented on by darren.worrall - I had some issues using pymssql from the repos (currently 1.0.1 in Karmic) - though I forget the exact errors. I updated to the latest version of the module (1.0,2) and it's been fine - might be worth trying that :) (fwiw, I use virtualenv to easily bottle up python dependencies) I had some issues using pymssql from the repos (currently 1.0.1 in Karmic) - though I forget the exact errors. I updated to the latest version of the module (1.0,2) and it's been fine - might be worth trying that :) (fwiw, I use virtualenv to easily bottle up python dependencies) Dec 15, 2009 issue 81 (Display schema prefix?) Status changed by albrecht.andi - r8a2fce9ea3dc Status: Fixed r8a2fce9ea3dc Status: Fixed Dec 15, 2009 issue 81 (Display schema prefix?) Labels changed by albrecht.andi - That's an good idea. Thanks! Labels: Version-Development Milestone-0.4.2 That's an good idea. Thanks! Labels: Version-Development Milestone-0.4.2 Dec 15, 2009 2 new revisions pushed by albrecht.andi - 98c4e116c9:Add __main__ stanza to cmdline.py, by Darran Worrall. 8a2fce9ea3:Provider proper schema information, fixes issue81 , patch by Darren Worrall. 98c4e116c9:Add __main__ stanza to cmdline.py, by Darran Worrall. 8a2fce9ea3:Provider proper schema information, fixes issue81 , patch by Darren Worrall. Dec 14, 2009 issue 39 (stringobject.c:4491: bad argument to internal function) commented on by albrecht.andi - Does this happen with every query or do some queries work? Does this happen with every query or do some queries work? Dec 14, 2009 issue 39 (stringobject.c:4491: bad argument to internal function) commented on by dunnomattic - I am having the same issue, as is a friend of mine. Using CrunchyFrog 0.4.1 from ppa repo on Kubuntu 9.10 (32-bit) with Python 2.6.4 Database type is SQL Server and Data Source -> Edit -> Test Connection works fine. Connection gets established normally. Executing any query produces the exact error as follows: - Query Failed (0.000 seconds) - ../Objects/stringobject.c:4640: bad argument to internal function I am having the same issue, as is a friend of mine. Using CrunchyFrog 0.4.1 from ppa repo on Kubuntu 9.10 (32-bit) with Python 2.6.4 Database type is SQL Server and Data Source -> Edit -> Test Connection works fine. Connection gets established normally. Executing any query produces the exact error as follows: - Query Failed (0.000 seconds) - ../Objects/stringobject.c:4640: bad argument to internal function Dec 14, 2009 issue 81 (Display schema prefix?) commented on by darren.worrall - It should be safe to apply this without worrying about the implications on the drivers I cant test, it will use the current behaviour if the .schema property is not found on the Table/View. Incidentally this also makes it trivial to apply to other backends when they can be tested (you just need to add schema=schema when instantiating the view/table) It should be safe to apply this without worrying about the implications on the drivers I cant test, it will use the current behaviour if the .schema property is not found on the Table/View. Incidentally this also makes it trivial to apply to other backends when they can be tested (you just need to add schema=schema when instantiating the view/table) Dec 14, 2009 issue 81 (Display schema prefix?) commented on by darren.worrall - Here's a small patch which will group/display the schemata correctly, and also prepend the correct schema when you drag and drop from the navigator. Tested and behaves correctly with MSSql, MySQL and SQLite (no access to Oracle or the others I'm afraid, though I'm not sure which (other than oracle) supports multiple schemas) Here's a small patch which will group/display the schemata correctly, and also prepend the correct schema when you drag and drop from the navigator. Tested and behaves correctly with MSSql, MySQL and SQLite (no access to Oracle or the others I'm afraid, though I'm not sure which (other than oracle) supports multiple schemas) Dec 10, 2009 issue 81 (Display schema prefix?) reported by darren.worrall - At least SQL server for example, supports multiple schemas per database, though in practice I've rarely seen it. However, using CF against the AdventureWorks sample database, I got caught out, as that has many schemas (Person/Production/Sales etc); for example, select * from Vendor fails, as it's not dbo.Vendor, it's Purchasing.Vendor You might want to consider having an option to display the schema prefix in the navigator (if you dont already anyway, I couldn't see one). Seems to be working quite well against my sql boxes now though, thanks a lot being responsive :) At least SQL server for example, supports multiple schemas per database, though in practice I've rarely seen it. However, using CF against the AdventureWorks sample database, I got caught out, as that has many schemas (Person/Production/Sales etc); for example, select * from Vendor fails, as it's not dbo.Vendor, it's Purchasing.Vendor You might want to consider having an option to display the schema prefix in the navigator (if you dont already anyway, I couldn't see one). Seems to be working quite well against my sql boxes now though, thanks a lot being responsive :) Dec 10, 2009 issue 79 (mssql issues; Set changed size during iteration and hangs at...) commented on by darren.worrall - Thanks :) I did a similar fix, was trying to see if I could dig deeper but I'll leave it now, debug fail was irritating anyway :) Thanks :) I did a similar fix, was trying to see if I could dig deeper but I'll leave it now, debug fail was irritating anyway :) Dec 10, 2009 issue 79 (mssql issues; Set changed size during iteration and hangs at...) changed by albrecht.andi - This issue was closed by revision d75abbdc95. Status: Fixed This issue was closed by revision d75abbdc95. Status: Fixed Dec 10, 2009 Revision d75abbdc95 (Search on copy of original item list (fixes issue79).) pushed by albrecht.andi - Search on copy of original item list (fixes issue79 ). Search on copy of original item list (fixes issue79 ). Dec 09, 2009 issue 80 ([patch]Cannot connect to SQL2005 - information_schema case s...) Labels changed by albrecht.andi - Labels: Version-Development Milestone-0.4.2 Labels: Version-Development Milestone-0.4.2 Dec 09, 2009 issue 80 ([patch]Cannot connect to SQL2005 - information_schema case s...) changed by albrecht.andi - This issue was closed by revision a1ffddd1f6. Status: Fixed This issue was closed by revision a1ffddd1f6. Status: Fixed Dec 09, 2009 Revision a1ffddd1f6 (Fix case-sensitive table names for initial SQL Server schema...) pushed by albrecht.andi - Fix case-sensitive table names for initial SQL Server schema query, by Darren Worrall (fixes issue80 )." Fix case-sensitive table names for initial SQL Server schema query, by Darren Worrall (fixes issue80 )." Dec 09, 2009 issue 79 (mssql issues; Set changed size during iteration and hangs at...) commented on by darren.worrall - I'm very regularly getting RuntimeError: Set changed size during iteration, but I cant get a debugger going in the relevant module. With a pdb.set_trace() (on line 85 (in cf.db.meta.find), I get a pdb prompt, but I cant actually type anything into it. Feels like some kind of race problem - any thoughts on where I should be looking? I'm very regularly getting RuntimeError: Set changed size during iteration, but I cant get a debugger going in the relevant module. With a pdb.set_trace() (on line 85 (in cf.db.meta.find), I get a pdb prompt, but I cant actually type anything into it. Feels like some kind of race problem - any thoughts on where I should be looking? Dec 09, 2009 issue 80 ([patch]Cannot connect to SQL2005 - information_schema case s...) reported by darren.worrall - In sql 2005, the system tables are hidden and cannot be directly queried, so the INITIAL_SQL query throws: Invalid object name 'information_schema.columns'. Simple fix though - the data is available through built in views, the names of which are upper case and case sensitive. Patch attached works on sql2000 and sql2005 In sql 2005, the system tables are hidden and cannot be directly queried, so the INITIAL_SQL query throws: Invalid object name 'information_schema.columns'. Simple fix though - the data is available through built in views, the names of which are upper case and case sensitive. Patch attached works on sql2000 and sql2005 Dec 09, 2009 issue 78 (set_status_message and pop_status_message duplicated in app....) commented on by darren.worrall - Ah, I posted issue 79 before I saw your reply, sorry about that :) I'm going to do my best to flesh out the problems - I'm desperate for a query editor on Linux that is reasonably engine neutral, and not many do SQL Server! Hadn't yet look at the interactive shell, certainly will do though, thanks for the tip Ah, I posted issue 79 before I saw your reply, sorry about that :) I'm going to do my best to flesh out the problems - I'm desperate for a query editor on Linux that is reasonably engine neutral, and not many do SQL Server! Hadn't yet look at the interactive shell, certainly will do though, thanks for the tip

issue 85 (Some PostgreSQL error messages break markup.) reported by albrecht.andi - What steps will reproduce the problem? 1. Try to open a connection to PostgreSQL where the database was deleted. What is the expected output? What do you see instead? A error message should appear, telling what went wrong. Instead a dialog "Failed" appears. 1263465896.003036 ERROR __init__.py:246 Datasource.dbconnect failed: Traceback (most recent call last): File "/storage/devel/cf/default/cf/db/__init__.py", line 235, in dbconnect conn = self._open_connection() File "/storage/devel/cf/default/cf/db/__init__.py", line 215, in _open_connection conn = self.backend.get_connection(self.url) File "/storage/devel/cf/default/cf/db/backends/__init__.py", line 134, in get_connection conn = self.dbapi().connect(*args, **kwds) OperationalError: FATAL: Datenbank >>XXX<< existiert nicht /storage/devel/cf/default/cf/ui/dialogs.py:52: GtkWarning: Failed to set text from markup due to error parsing markup: Error on line 1 char 112: Odd character 'n', expected a '=' after attribute name 'existiert' of element '<' dlg.format_secondary_markup(long) Please use labels and text to provide additional information.

What steps will reproduce the problem? 1. Try to open a connection to PostgreSQL where the database was deleted. What is the expected output? What do you see instead? A error message should appear, telling what went wrong. Instead a dialog "Failed" appears. 1263465896.003036 ERROR __init__.py:246 Datasource.dbconnect failed: Traceback (most recent call last): File "/storage/devel/cf/default/cf/db/__init__.py", line 235, in dbconnect conn = self._open_connection() File "/storage/devel/cf/default/cf/db/__init__.py", line 215, in _open_connection conn = self.backend.get_connection(self.url) File "/storage/devel/cf/default/cf/db/backends/__init__.py", line 134, in get_connection conn = self.dbapi().connect(*args, **kwds) OperationalError: FATAL: Datenbank >>XXX<< existiert nicht /storage/devel/cf/default/cf/ui/dialogs.py:52: GtkWarning: Failed to set text from markup due to error parsing markup: Error on line 1 char 112: Odd character 'n', expected a '=' after attribute name 'existiert' of element '<' dlg.format_secondary_markup(long) Please use labels and text to provide additional information.

Last 30 days

Earlier this year

Older