Menu
▾
▴
eclipsesql-bugs — Bugs are forwarded to this list - DO NOT EMAIL IT DIRECTLY!
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(19) |
Nov
(6) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(11) |
Nov
(37) |
Dec
(6) |
| 2009 |
Jan
(4) |
Feb
(18) |
Mar
(11) |
Apr
|
May
(8) |
Jun
(1) |
Jul
(6) |
Aug
(5) |
Sep
(3) |
Oct
(11) |
Nov
(9) |
Dec
(2) |
| 2010 |
Jan
|
Feb
(4) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(39) |
Aug
|
Sep
(8) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
(4) |
Feb
(2) |
Mar
(2) |
Apr
(6) |
May
(4) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
|
Oct
(15) |
Nov
(1) |
Dec
(6) |
| 2012 |
Jan
(2) |
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
|
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2013-04-29 15:32:11
|
Bugs item #3612193, was opened at 2013-04-29 06:56 Message generated for change (Settings changed) made by hhilbert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3612193&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: BraileTrail (brailetrail) Assigned to: Heiko Hilbert (hhilbert) Summary: MySQL 5.6 does not accept "SET OPTION..." Initial Comment: MySQL 5.6 no longer accepts the syntax "SET OPTION SQL_SELECT_LIMIT=", it should now be "SET SQL_SELECT_LIMIT=". To reproduce the problem point SQLExplorer at a MySQL 5.6 instance and execute any command in an SQL Editor window, for example "use mysql" and you get the error: "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=100' at line 1" This seems to be issued by SQLExplorer before trying to execute my query and I don't believe that I have any control the SQL generated by SQLExplorer. It also seems that mysqldump sufferes from this problem: http://bugs.mysql.com/bug.php?id=67507 ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2013-04-29 08:31 Message: Thx for the response :-) ---------------------------------------------------------------------- Comment By: BraileTrail (brailetrail) Date: 2013-04-29 08:03 Message: DOH! I had edited the JDBC driver within SQLExplorer to point at the latest jar file and it didn't make any difference, but I hadn't restart SQL Explorer at the time. I have just restarted SQLExplorer and it's fine with the new driver. Apologies. ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2013-04-29 07:10 Message: This seems to be a JDBC-Driver issue. SQLExplorer calls: stmt.setMaxRows(maxRows); where stmt is a java.sql.Statement retrieved form the JDBC-Driver. Check if you are using the latest Connector/J from MySql: http://dev.mysql.com/downloads/connector/j/ As workaround you can switch off the checkbox 'Limit Rows' in SQL-Editor toolbar and add a LIMIT clause to your sql statement. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3612193&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2013-04-29 15:31:51
|
Bugs item #3612193, was opened at 2013-04-29 06:56 Message generated for change (Comment added) made by hhilbert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3612193&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Wont Fix Priority: 5 Private: No Submitted By: BraileTrail (brailetrail) Assigned to: Heiko Hilbert (hhilbert) Summary: MySQL 5.6 does not accept "SET OPTION..." Initial Comment: MySQL 5.6 no longer accepts the syntax "SET OPTION SQL_SELECT_LIMIT=", it should now be "SET SQL_SELECT_LIMIT=". To reproduce the problem point SQLExplorer at a MySQL 5.6 instance and execute any command in an SQL Editor window, for example "use mysql" and you get the error: "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=100' at line 1" This seems to be issued by SQLExplorer before trying to execute my query and I don't believe that I have any control the SQL generated by SQLExplorer. It also seems that mysqldump sufferes from this problem: http://bugs.mysql.com/bug.php?id=67507 ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2013-04-29 08:31 Message: Thx for the response :-) ---------------------------------------------------------------------- Comment By: BraileTrail (brailetrail) Date: 2013-04-29 08:03 Message: DOH! I had edited the JDBC driver within SQLExplorer to point at the latest jar file and it didn't make any difference, but I hadn't restart SQL Explorer at the time. I have just restarted SQLExplorer and it's fine with the new driver. Apologies. ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2013-04-29 07:10 Message: This seems to be a JDBC-Driver issue. SQLExplorer calls: stmt.setMaxRows(maxRows); where stmt is a java.sql.Statement retrieved form the JDBC-Driver. Check if you are using the latest Connector/J from MySql: http://dev.mysql.com/downloads/connector/j/ As workaround you can switch off the checkbox 'Limit Rows' in SQL-Editor toolbar and add a LIMIT clause to your sql statement. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3612193&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2013-04-29 15:04:00
|
Bugs item #3612193, was opened at 2013-04-29 06:56 Message generated for change (Comment added) made by brailetrail You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3612193&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Wont Fix Priority: 5 Private: No Submitted By: BraileTrail (brailetrail) Assigned to: Heiko Hilbert (hhilbert) Summary: MySQL 5.6 does not accept "SET OPTION..." Initial Comment: MySQL 5.6 no longer accepts the syntax "SET OPTION SQL_SELECT_LIMIT=", it should now be "SET SQL_SELECT_LIMIT=". To reproduce the problem point SQLExplorer at a MySQL 5.6 instance and execute any command in an SQL Editor window, for example "use mysql" and you get the error: "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=100' at line 1" This seems to be issued by SQLExplorer before trying to execute my query and I don't believe that I have any control the SQL generated by SQLExplorer. It also seems that mysqldump sufferes from this problem: http://bugs.mysql.com/bug.php?id=67507 ---------------------------------------------------------------------- >Comment By: BraileTrail (brailetrail) Date: 2013-04-29 08:03 Message: DOH! I had edited the JDBC driver within SQLExplorer to point at the latest jar file and it didn't make any difference, but I hadn't restart SQL Explorer at the time. I have just restarted SQLExplorer and it's fine with the new driver. Apologies. ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2013-04-29 07:10 Message: This seems to be a JDBC-Driver issue. SQLExplorer calls: stmt.setMaxRows(maxRows); where stmt is a java.sql.Statement retrieved form the JDBC-Driver. Check if you are using the latest Connector/J from MySql: http://dev.mysql.com/downloads/connector/j/ As workaround you can switch off the checkbox 'Limit Rows' in SQL-Editor toolbar and add a LIMIT clause to your sql statement. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3612193&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2013-04-29 14:11:49
|
Bugs item #3612193, was opened at 2013-04-29 06:56 Message generated for change (Settings changed) made by hhilbert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3612193&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Resolution: Wont Fix Priority: 5 Private: No Submitted By: BraileTrail (brailetrail) >Assigned to: Heiko Hilbert (hhilbert) Summary: MySQL 5.6 does not accept "SET OPTION..." Initial Comment: MySQL 5.6 no longer accepts the syntax "SET OPTION SQL_SELECT_LIMIT=", it should now be "SET SQL_SELECT_LIMIT=". To reproduce the problem point SQLExplorer at a MySQL 5.6 instance and execute any command in an SQL Editor window, for example "use mysql" and you get the error: "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=100' at line 1" This seems to be issued by SQLExplorer before trying to execute my query and I don't believe that I have any control the SQL generated by SQLExplorer. It also seems that mysqldump sufferes from this problem: http://bugs.mysql.com/bug.php?id=67507 ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2013-04-29 07:10 Message: This seems to be a JDBC-Driver issue. SQLExplorer calls: stmt.setMaxRows(maxRows); where stmt is a java.sql.Statement retrieved form the JDBC-Driver. Check if you are using the latest Connector/J from MySql: http://dev.mysql.com/downloads/connector/j/ As workaround you can switch off the checkbox 'Limit Rows' in SQL-Editor toolbar and add a LIMIT clause to your sql statement. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3612193&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2013-04-29 14:10:20
|
Bugs item #3612193, was opened at 2013-04-29 06:56 Message generated for change (Comment added) made by hhilbert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3612193&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: BraileTrail (brailetrail) Assigned to: Nobody/Anonymous (nobody) Summary: MySQL 5.6 does not accept "SET OPTION..." Initial Comment: MySQL 5.6 no longer accepts the syntax "SET OPTION SQL_SELECT_LIMIT=", it should now be "SET SQL_SELECT_LIMIT=". To reproduce the problem point SQLExplorer at a MySQL 5.6 instance and execute any command in an SQL Editor window, for example "use mysql" and you get the error: "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=100' at line 1" This seems to be issued by SQLExplorer before trying to execute my query and I don't believe that I have any control the SQL generated by SQLExplorer. It also seems that mysqldump sufferes from this problem: http://bugs.mysql.com/bug.php?id=67507 ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2013-04-29 07:10 Message: This seems to be a JDBC-Driver issue. SQLExplorer calls: stmt.setMaxRows(maxRows); where stmt is a java.sql.Statement retrieved form the JDBC-Driver. Check if you are using the latest Connector/J from MySql: http://dev.mysql.com/downloads/connector/j/ As workaround you can switch off the checkbox 'Limit Rows' in SQL-Editor toolbar and add a LIMIT clause to your sql statement. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3612193&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2013-04-29 13:56:01
|
Bugs item #3612193, was opened at 2013-04-29 06:56 Message generated for change (Tracker Item Submitted) made by brailetrail You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3612193&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: BraileTrail (brailetrail) Assigned to: Nobody/Anonymous (nobody) Summary: MySQL 5.6 does not accept "SET OPTION..." Initial Comment: MySQL 5.6 no longer accepts the syntax "SET OPTION SQL_SELECT_LIMIT=", it should now be "SET SQL_SELECT_LIMIT=". To reproduce the problem point SQLExplorer at a MySQL 5.6 instance and execute any command in an SQL Editor window, for example "use mysql" and you get the error: "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=100' at line 1" This seems to be issued by SQLExplorer before trying to execute my query and I don't believe that I have any control the SQL generated by SQLExplorer. It also seems that mysqldump sufferes from this problem: http://bugs.mysql.com/bug.php?id=67507 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3612193&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2012-09-09 15:46:16
|
Bugs item #3562208, was opened at 2012-08-27 08:58 Message generated for change (Comment added) made by hhilbert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3562208&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: https://www.google.com/accounts () >Assigned to: Heiko Hilbert (hhilbert) Summary: NPE without dbo. Initial Comment: Eclipse Indigo SR2 Sybase ASE 15.7 SQL Explorer 3.6.1 plug-in jtds-1.2.5 Getting NPE (stack trace below) under various circumstances. On each occasion I\'m starting Eclispe afresh, then right-click on DB->New SQL Editor 1) rollback without any prior command to rollback 2) use select * from sysobjects Only when I add dbo. in front of the table name can I avoid the NPE. Doesn\'t matter what DB it is. I\'m using sa so would think I would get god permissions? !ENTRY net.sourceforge.sqlexplorer 4 4 2012-08-27 16:33:47.203 !MESSAGE Error executing. !STACK 0 java.lang.NullPointerException at net.sourceforge.sqlexplorer.history.SQLHistory.addSQL(SQLHistory.java:130) at net.sourceforge.sqlexplorer.sqlpanel.SQLExecution.logHistory(SQLExecution.java:322) at net.sourceforge.sqlexplorer.sqlpanel.SQLExecution.startQuery(SQLExecution.java:338) at net.sourceforge.sqlexplorer.sqlpanel.SQLExecution.doExecution(SQLExecution.java:216) at net.sourceforge.sqlexplorer.sqlpanel.AbstractSQLExecution.run(AbstractSQLExecution.java:116) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) ---------------------------------------------------------------------- >Comment By: Heiko Hilbert (hhilbert) Date: 2012-09-09 08:46 Message: Fix is committed ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2012-08-28 03:32 Message: This is a bug in the SQL History if you renamed or deleted a database alias. As workaround you can clear your SQL History by using the context menu 'Remove all from History' in the SQL History view. See also here: https://sourceforge.net/projects/eclipsesql/forums/forum/450662/topic/5505091 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3562208&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2012-09-07 17:23:47
|
Bugs item #3466577, was opened at 2011-12-28 13:52 Message generated for change (Comment added) made by siking1 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3466577&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark (siking1) Assigned to: Nobody/Anonymous (nobody) Summary: GUI freezes when connection times out Initial Comment: Running: - Linux Mint 12 (AMD64) - Eclipse 3.7.1 - OpenJDK 1.6.0_23-b23 - SQL Explorer 3.6.1 - db2jcc4-9.7.100.177.jar connector Open a connection to a database, and allow the connection to time out. After time out, try to close the connection. The entire GUI freezes up and has to be force-killed. FYI: I have seen this exact same behaviour with SQuirreL, which I believe SQL Explorer is at least partially based on. ---------------------------------------------------------------------- >Comment By: Mark (siking1) Date: 2012-09-07 10:23 Message: Hey again. Even after setting the Close unused connections after (seconds) to 60, I still kept running into this issue, until ... I also tuned on AutoCommit (under Create / Edit User Details). This seems to have made the problem go away. :) ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2012-01-20 12:07 Message: You can check the possible parameters for your db2 JDBC driver. Perhaps you can define connection timeouts there. Or there are java system properties that could be set fpr your driver? ---------------------------------------------------------------------- Comment By: Mark (siking1) Date: 2012-01-20 10:36 Message: I am still hitting this issue, even after the above suggested workaround. I can provide additional information, but I do not know what would be relevant. ---------------------------------------------------------------------- Comment By: Mark (siking1) Date: 2011-12-29 15:04 Message: Thanx hhilbert. I have been running with this all day, and it works perfect. Happy holidays! ;) ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2011-12-29 01:18 Message: Probably this is a problem with the underlying db2 JDBC driver. The call to close the connection on a timed out connection will never return. A workaround is to use the new preference: Close unused connections after (seconds) If you set it to a value lesser then the db2 connection timeout the connection is closed before time out. If you don't need connection specific db values like temp tables or sql session values you can set this value as small aus you like. SQL Explorer creates a new connection if required. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3466577&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2012-08-28 10:32:18
|
Bugs item #3562208, was opened at 2012-08-27 08:58 Message generated for change (Comment added) made by hhilbert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3562208&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: https://www.google.com/accounts () Assigned to: Nobody/Anonymous (nobody) Summary: NPE without dbo. Initial Comment: Eclipse Indigo SR2 Sybase ASE 15.7 SQL Explorer 3.6.1 plug-in jtds-1.2.5 Getting NPE (stack trace below) under various circumstances. On each occasion I\'m starting Eclispe afresh, then right-click on DB->New SQL Editor 1) rollback without any prior command to rollback 2) use select * from sysobjects Only when I add dbo. in front of the table name can I avoid the NPE. Doesn\'t matter what DB it is. I\'m using sa so would think I would get god permissions? !ENTRY net.sourceforge.sqlexplorer 4 4 2012-08-27 16:33:47.203 !MESSAGE Error executing. !STACK 0 java.lang.NullPointerException at net.sourceforge.sqlexplorer.history.SQLHistory.addSQL(SQLHistory.java:130) at net.sourceforge.sqlexplorer.sqlpanel.SQLExecution.logHistory(SQLExecution.java:322) at net.sourceforge.sqlexplorer.sqlpanel.SQLExecution.startQuery(SQLExecution.java:338) at net.sourceforge.sqlexplorer.sqlpanel.SQLExecution.doExecution(SQLExecution.java:216) at net.sourceforge.sqlexplorer.sqlpanel.AbstractSQLExecution.run(AbstractSQLExecution.java:116) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) ---------------------------------------------------------------------- >Comment By: Heiko Hilbert (hhilbert) Date: 2012-08-28 03:32 Message: This is a bug in the SQL History if you renamed or deleted a database alias. As workaround you can clear your SQL History by using the context menu 'Remove all from History' in the SQL History view. See also here: https://sourceforge.net/projects/eclipsesql/forums/forum/450662/topic/5505091 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3562208&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2012-08-27 15:58:56
|
Bugs item #3562208, was opened at 2012-08-27 08:58 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3562208&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: https://www.google.com/accounts () Assigned to: Nobody/Anonymous (nobody) Summary: NPE without dbo. Initial Comment: Eclipse Indigo SR2 Sybase ASE 15.7 SQL Explorer 3.6.1 plug-in jtds-1.2.5 Getting NPE (stack trace below) under various circumstances. On each occasion I\'m starting Eclispe afresh, then right-click on DB->New SQL Editor 1) rollback without any prior command to rollback 2) use select * from sysobjects Only when I add dbo. in front of the table name can I avoid the NPE. Doesn\'t matter what DB it is. I\'m using sa so would think I would get god permissions? !ENTRY net.sourceforge.sqlexplorer 4 4 2012-08-27 16:33:47.203 !MESSAGE Error executing. !STACK 0 java.lang.NullPointerException at net.sourceforge.sqlexplorer.history.SQLHistory.addSQL(SQLHistory.java:130) at net.sourceforge.sqlexplorer.sqlpanel.SQLExecution.logHistory(SQLExecution.java:322) at net.sourceforge.sqlexplorer.sqlpanel.SQLExecution.startQuery(SQLExecution.java:338) at net.sourceforge.sqlexplorer.sqlpanel.SQLExecution.doExecution(SQLExecution.java:216) at net.sourceforge.sqlexplorer.sqlpanel.AbstractSQLExecution.run(AbstractSQLExecution.java:116) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3562208&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2012-07-25 13:04:38
|
Bugs item #3542624, was opened at 2012-07-11 10:33 Message generated for change (Comment added) made by joshballz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3542624&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: cardonbj (cardonbj) Assigned to: Nobody/Anonymous (nobody) Summary: In Juno, 'Database Structure' view does not work Initial Comment: In the new Juno release of Eclipse SDK, the Database Structure view does not seem to show anything. This may be a side effect of the fact that connecting to a database also no longer immediately opens a new SQL Editor window. ---------------------------------------------------------------------- Comment By: joshballz (joshballz) Date: 2012-07-25 06:04 Message: Closing the database structure window and then opening it again from the right click menu on the database connection will display a working database structure. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3542624&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2012-07-11 17:33:57
|
Bugs item #3542624, was opened at 2012-07-11 10:33 Message generated for change (Tracker Item Submitted) made by cardonbj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3542624&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: cardonbj (cardonbj) Assigned to: Nobody/Anonymous (nobody) Summary: In Juno, 'Database Structure' view does not work Initial Comment: In the new Juno release of Eclipse SDK, the Database Structure view does not seem to show anything. This may be a side effect of the fact that connecting to a database also no longer immediately opens a new SQL Editor window. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3542624&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2012-05-14 14:42:31
|
Bugs item #3526587, was opened at 2012-05-14 07:42 Message generated for change (Tracker Item Submitted) made by thomas-z-meyer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3526587&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Thomas Meyer (thomas-z-meyer) Assigned to: Nobody/Anonymous (nobody) Summary: OutOfMemoryError for larg sql file (syntax highlighting?) Initial Comment: SQLExplorer crashes with java.lang.OutOfMemoryError: Java heap space because of Syntax highlighthing in slightly larger files. I wanted to open a file with around 40.000 SQL insert statements. When I open the same file with the normal Eclipse text editor I don't get any problems, but when I open the same file with the SQL Editor I get this stack trace: java.lang.OutOfMemoryError: Java heap space at java.util.ArrayList.<init>(Unknown Source) at org.eclipse.jface.text.TextViewer.applyTextPresentation(TextViewer.java:4824) at org.eclipse.jface.text.TextViewer.changeTextPresentation(TextViewer.java:4888) at org.eclipse.jface.text.presentation.PresentationReconciler.applyTextRegionCollection(PresentationReconciler.java:579) at org.eclipse.jface.text.presentation.PresentationReconciler.processDamage(PresentationReconciler.java:568) at org.eclipse.jface.text.presentation.PresentationReconciler.access$3(PresentationReconciler.java:564) at org.eclipse.jface.text.presentation.PresentationReconciler$InternalListener.inputDocumentChanged(PresentationReconciler.java:119) at org.eclipse.jface.text.TextViewer.fireInputDocumentChanged(TextViewer.java:2888) at org.eclipse.jface.text.TextViewer.setDocument(TextViewer.java:2937) at org.eclipse.jface.text.source.SourceViewer.setDocument(SourceViewer.java:640) at org.eclipse.jface.text.source.SourceViewer.setDocument(SourceViewer.java:574) at net.sourceforge.sqlexplorer.sqleditor.SQLTextViewer.setDocument(SQLTextViewer.java:184) at net.sourceforge.sqlexplorer.sqleditor.SQLTextViewer.setDocument(SQLTextViewer.java:204) at org.eclipse.ui.texteditor.AbstractTextEditor.initializeSourceViewer(AbstractTextEditor.java:4030) at org.eclipse.ui.texteditor.AbstractTextEditor.createPartControl(AbstractTextEditor.java:3558) at org.eclipse.ui.texteditor.StatusTextEditor.createPartControl(StatusTextEditor.java:54) at org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.createPartControl(AbstractDecoratedTextEditor.java:440) at net.sourceforge.sqlexplorer.plugin.editors.SQLTextEditor.createPartControl(SQLTextEditor.java:131) at net.sourceforge.sqlexplorer.plugin.editors.SQLEditor.createEditor(SQLEditor.java:339) at net.sourceforge.sqlexplorer.plugin.editors.SQLEditor.createPartControl(SQLEditor.java:242) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:289) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2945) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2850) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2842) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2793) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2789) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2773) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2756) SQLExplore should disable syntax highlighting for files of a given size. SQLExplore version is: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3526587&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2012-04-12 08:39:59
|
Bugs item #3434838, was opened at 2011-11-08 00:42 Message generated for change (Comment added) made by hhilbert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3434838&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: LongTTH (longtth) >Assigned to: Heiko Hilbert (hhilbert) Summary: disable case sensitive for database structure Initial Comment: Please disable case sensitive for the database strucutre tab, cause it make an "asp_net_membership table" display after "Staff table" (detail in attachment) ---------------------------------------------------------------------- >Comment By: Heiko Hilbert (hhilbert) Date: 2012-04-12 01:39 Message: fixed with 3.6.1 SR4 P1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3434838&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2012-04-12 08:38:32
|
Bugs item #3462633, was opened at 2011-12-19 17:07 Message generated for change (Comment added) made by hhilbert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3462633&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Andrew E. Schulman (schulman) Assigned to: Heiko Hilbert (hhilbert) Summary: tab delimiter is broken in export to CSV Initial Comment: EclipseSQL 3.6.1.v20111007_SR4_P1. In a query result or table preview window, if I select the \"Export to CSV\" option and then choose \"\\t [TAB]\" as the delimiter, then instead of inserting tab characters in the output as expected, EclipseSQL inserts the literal string \"\\t [TAB]\". ---------------------------------------------------------------------- >Comment By: Heiko Hilbert (hhilbert) Date: 2012-04-12 01:38 Message: Fixed with 3.6.1 SR5 ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2011-12-20 07:18 Message: will be fixed with next release ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3462633&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2012-01-20 20:07:05
|
Bugs item #3466577, was opened at 2011-12-28 13:52 Message generated for change (Comment added) made by hhilbert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3466577&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark (siking1) Assigned to: Nobody/Anonymous (nobody) Summary: GUI freezes when connection times out Initial Comment: Running: - Linux Mint 12 (AMD64) - Eclipse 3.7.1 - OpenJDK 1.6.0_23-b23 - SQL Explorer 3.6.1 - db2jcc4-9.7.100.177.jar connector Open a connection to a database, and allow the connection to time out. After time out, try to close the connection. The entire GUI freezes up and has to be force-killed. FYI: I have seen this exact same behaviour with SQuirreL, which I believe SQL Explorer is at least partially based on. ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2012-01-20 12:07 Message: You can check the possible parameters for your db2 JDBC driver. Perhaps you can define connection timeouts there. Or there are java system properties that could be set fpr your driver? ---------------------------------------------------------------------- Comment By: Mark (siking1) Date: 2012-01-20 10:36 Message: I am still hitting this issue, even after the above suggested workaround. I can provide additional information, but I do not know what would be relevant. ---------------------------------------------------------------------- Comment By: Mark (siking1) Date: 2011-12-29 15:04 Message: Thanx hhilbert. I have been running with this all day, and it works perfect. Happy holidays! ;) ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2011-12-29 01:18 Message: Probably this is a problem with the underlying db2 JDBC driver. The call to close the connection on a timed out connection will never return. A workaround is to use the new preference: Close unused connections after (seconds) If you set it to a value lesser then the db2 connection timeout the connection is closed before time out. If you don't need connection specific db values like temp tables or sql session values you can set this value as small aus you like. SQL Explorer creates a new connection if required. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3466577&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2012-01-20 18:36:50
|
Bugs item #3466577, was opened at 2011-12-28 13:52 Message generated for change (Comment added) made by siking1 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3466577&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark (siking1) Assigned to: Nobody/Anonymous (nobody) Summary: GUI freezes when connection times out Initial Comment: Running: - Linux Mint 12 (AMD64) - Eclipse 3.7.1 - OpenJDK 1.6.0_23-b23 - SQL Explorer 3.6.1 - db2jcc4-9.7.100.177.jar connector Open a connection to a database, and allow the connection to time out. After time out, try to close the connection. The entire GUI freezes up and has to be force-killed. FYI: I have seen this exact same behaviour with SQuirreL, which I believe SQL Explorer is at least partially based on. ---------------------------------------------------------------------- >Comment By: Mark (siking1) Date: 2012-01-20 10:36 Message: I am still hitting this issue, even after the above suggested workaround. I can provide additional information, but I do not know what would be relevant. ---------------------------------------------------------------------- Comment By: Mark (siking1) Date: 2011-12-29 15:04 Message: Thanx hhilbert. I have been running with this all day, and it works perfect. Happy holidays! ;) ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2011-12-29 01:18 Message: Probably this is a problem with the underlying db2 JDBC driver. The call to close the connection on a timed out connection will never return. A workaround is to use the new preference: Close unused connections after (seconds) If you set it to a value lesser then the db2 connection timeout the connection is closed before time out. If you don't need connection specific db values like temp tables or sql session values you can set this value as small aus you like. SQL Explorer creates a new connection if required. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3466577&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2011-12-29 23:04:13
|
Bugs item #3466577, was opened at 2011-12-28 13:52 Message generated for change (Comment added) made by siking1 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3466577&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark (siking1) Assigned to: Nobody/Anonymous (nobody) Summary: GUI freezes when connection times out Initial Comment: Running: - Linux Mint 12 (AMD64) - Eclipse 3.7.1 - OpenJDK 1.6.0_23-b23 - SQL Explorer 3.6.1 - db2jcc4-9.7.100.177.jar connector Open a connection to a database, and allow the connection to time out. After time out, try to close the connection. The entire GUI freezes up and has to be force-killed. FYI: I have seen this exact same behaviour with SQuirreL, which I believe SQL Explorer is at least partially based on. ---------------------------------------------------------------------- >Comment By: Mark (siking1) Date: 2011-12-29 15:04 Message: Thanx hhilbert. I have been running with this all day, and it works perfect. Happy holidays! ;) ---------------------------------------------------------------------- Comment By: Heiko Hilbert (hhilbert) Date: 2011-12-29 01:18 Message: Probably this is a problem with the underlying db2 JDBC driver. The call to close the connection on a timed out connection will never return. A workaround is to use the new preference: Close unused connections after (seconds) If you set it to a value lesser then the db2 connection timeout the connection is closed before time out. If you don't need connection specific db values like temp tables or sql session values you can set this value as small aus you like. SQL Explorer creates a new connection if required. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3466577&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2011-12-29 09:18:48
|
Bugs item #3466577, was opened at 2011-12-28 13:52 Message generated for change (Comment added) made by hhilbert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3466577&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark (siking1) Assigned to: Nobody/Anonymous (nobody) Summary: GUI freezes when connection times out Initial Comment: Running: - Linux Mint 12 (AMD64) - Eclipse 3.7.1 - OpenJDK 1.6.0_23-b23 - SQL Explorer 3.6.1 - db2jcc4-9.7.100.177.jar connector Open a connection to a database, and allow the connection to time out. After time out, try to close the connection. The entire GUI freezes up and has to be force-killed. FYI: I have seen this exact same behaviour with SQuirreL, which I believe SQL Explorer is at least partially based on. ---------------------------------------------------------------------- >Comment By: Heiko Hilbert (hhilbert) Date: 2011-12-29 01:18 Message: Probably this is a problem with the underlying db2 JDBC driver. The call to close the connection on a timed out connection will never return. A workaround is to use the new preference: Close unused connections after (seconds) If you set it to a value lesser then the db2 connection timeout the connection is closed before time out. If you don't need connection specific db values like temp tables or sql session values you can set this value as small aus you like. SQL Explorer creates a new connection if required. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3466577&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2011-12-28 21:52:08
|
Bugs item #3466577, was opened at 2011-12-28 13:52 Message generated for change (Tracker Item Submitted) made by siking1 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3466577&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark (siking1) Assigned to: Nobody/Anonymous (nobody) Summary: GUI freezes when connection times out Initial Comment: Running: - Linux Mint 12 (AMD64) - Eclipse 3.7.1 - OpenJDK 1.6.0_23-b23 - SQL Explorer 3.6.1 - db2jcc4-9.7.100.177.jar connector Open a connection to a database, and allow the connection to time out. After time out, try to close the connection. The entire GUI freezes up and has to be force-killed. FYI: I have seen this exact same behaviour with SQuirreL, which I believe SQL Explorer is at least partially based on. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3466577&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2011-12-22 19:39:17
|
Bugs item #3464075, was opened at 2011-12-22 11:39 Message generated for change (Tracker Item Submitted) made by siking1 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3464075&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark (siking1) Assigned to: Nobody/Anonymous (nobody) Summary: 3004: Unexpected error occured Initial Comment: Running: - Linux Mint 12 (AMD64) - Eclipse 3.7.1 - OpenJDK 1.6.0_23-b23 - SQL Explorer 3.6.1 - db2jcc4-9.7.100.177.jar connector 1) Connect to the database. 2) In the tree view open the tables tree. 3004: Unexpected error occurred. java.lang.RuntimeException at org.eclipse.jface.viewers.ColumnViewer.checkBusy(ColumnViewer.java:763) at org.eclipse.jface.viewers.ColumnViewer.update(ColumnViewer.java:552) at net.sourceforge.sqlexplorer.plugin.views.DatabaseStructureView$6.treeExpanded(DatabaseStructureView.java:339) at org.eclipse.jface.viewers.AbstractTreeViewer$3.run(AbstractTreeViewer.java:1107) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.AbstractTreeViewer.fireTreeExpanded(AbstractTreeViewer.java:1105) at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1487) at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:952) at org.eclipse.jface.viewers.AbstractTreeViewer$4.treeExpanded(AbstractTreeViewer.java:1496) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:132) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267) at org.eclipse.swt.widgets.Tree.gtk_test_expand_row(Tree.java:2130) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1775) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4414) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8422) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1245) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2276) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3207) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3464075&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2011-12-20 15:18:28
|
Bugs item #3462633, was opened at 2011-12-19 17:07 Message generated for change (Comment added) made by hhilbert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3462633&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Andrew E. Schulman (schulman) >Assigned to: Heiko Hilbert (hhilbert) Summary: tab delimiter is broken in export to CSV Initial Comment: EclipseSQL 3.6.1.v20111007_SR4_P1. In a query result or table preview window, if I select the \"Export to CSV\" option and then choose \"\\t [TAB]\" as the delimiter, then instead of inserting tab characters in the output as expected, EclipseSQL inserts the literal string \"\\t [TAB]\". ---------------------------------------------------------------------- >Comment By: Heiko Hilbert (hhilbert) Date: 2011-12-20 07:18 Message: will be fixed with next release ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3462633&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2011-12-20 01:07:38
|
Bugs item #3462633, was opened at 2011-12-19 17:07 Message generated for change (Tracker Item Submitted) made by schulman You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3462633&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Andrew E. Schulman (schulman) Assigned to: Nobody/Anonymous (nobody) Summary: tab delimiter is broken in export to CSV Initial Comment: EclipseSQL 3.6.1.v20111007_SR4_P1. In a query result or table preview window, if I select the \"Export to CSV\" option and then choose \"\\t [TAB]\" as the delimiter, then instead of inserting tab characters in the output as expected, EclipseSQL inserts the literal string \"\\t [TAB]\". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3462633&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2011-11-08 08:42:00
|
Bugs item #3434838, was opened at 2011-11-08 00:42 Message generated for change (Tracker Item Submitted) made by longtth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3434838&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: LongTTH (longtth) Assigned to: Nobody/Anonymous (nobody) Summary: disable case sensitive for database structure Initial Comment: Please disable case sensitive for the database strucutre tab, cause it make an "asp_net_membership table" display after "Staff table" (detail in attachment) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3434838&group_id=132863 |
|
From: SourceForge.net <no...@so...> - 2011-10-19 17:54:35
|
Bugs item #3426001, was opened at 2011-10-19 16:58 Message generated for change (Comment added) made by hhilbert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3426001&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: eugene (kulinek) >Assigned to: Heiko Hilbert (hhilbert) Summary: failure to close connections Initial Comment: I tested several times - With Eclipse+sqlexplorer plugin I connect to JavaDB using embedded driver (from JDK 1.6.27) using derby.jar (new profile had to be created). Once connected I disconnect. That works fine. I go to SQLExplorer app (with eclipse built in) and try to connect but I get exception saying that there is someone else already connected. However, if I close the eclipse+plugin I can connect with SQLExplorer app. That means the connection was not released until I closed eclipse+plugin Note that JavaDB embedded allows only one connection to DB. ---------------------------------------------------------------------- >Comment By: Heiko Hilbert (hhilbert) Date: 2011-10-19 19:54 Message: That is not a bug. It is because you are using the embedded driver. Which mean you have started a 'database server' in that JVM on your data filese. So after opening one connection the 'database server' is started and will reelase the databse files only if you shutdown the embedded database or close the VM. Here: http://db.apache.org/derby/papers/DerbyTut/embedded_intro.html#shutdown you can find this: >>>> Derby supports multiple connections to a given database. An example of an embedded application that manages concurrent users is a Tomcat or Geronimo application server that embeds Derby. Any number of users can execute Web applications that access a database through that Web server. However, only one JVM may boot ("open") that database, so multiple applications running in different JVMs cannot access the same database. <<<<<< Your solution could be to use the Derby network server and network client. This is described here: http://db.apache.org/derby/papers/DerbyTut/ns_intro.html Regards Heiko ---------------------------------------------------------------------- Comment By: eugene (kulinek) Date: 2011-10-19 17:19 Message: Same happens if I use SQL Explorer and Eclipse DTP. Closing connections does not release resources and the other app cannot connect until I actually shut down the whole app. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3426001&group_id=132863 |