squirrel-sql-develop Mailing List for SQuirreL SQL Client (Page 15)

Hi everyone,
 
I've just checked in a fix for this. It certainly now works for my
usecase below, and for other usages I could test. There is a comment in
the code stating the original problems came from the Intersystems Cache
Driver - I don't know that so couldn't test specifically that however I
think it should still work for that.
 
Neville

________________________________

From: Rowe, Neville 
Sent: 05 June 2009 15:11
To: squ...@li...
Subject: Stored procedure with multiple result sets


Hi everyone,

I've been running into a problem with stored procedures which return
multiple results sets when there are updates between each select
statement. On at least MS SQL Server, Sybase ASE and Sybase IQ (I've
tested on these three platforms) the following stored proc should return
two results sets however Squirrel is missing out the second set.

drop procedure nprTest;
create procedure nprTest as
    begin
    create table #tmp1 (tmpCol int)
    insert into #tmp1 values(1)
    select count(*) from #tmp1
    insert into #tmp1 values(2)
    select count(*) from #tmp1
    end;
exec nprTest;

Note it is the existence of the insert between the two select statements
which is causing this to happen - two sets are displayed if the insert
is missing.

The error seems to be in processQuery in
net.sourceforge.squirrel_sql.client.session.SQLExecuterTask - the notes
in the source indicate this has been problematic in the past, and indeed
there are significant changes from the code I originally contributed for
v1.2beta5...... Having had a quick glance the purpose of some of the
current code is not clear to me.

So before I try and work out a good solution to this, anyone else have
any opinions or test cases which the existing code is supposed to work
around ?

Thanks,

Neville 
This e-mail is confidential and the information contained in it may be
privileged. It should not be read, copied or used by anyone other than the
intended recipient.  If you have received it in error, please contact the sender
immediately by telephoning (+44 (0)20 7623 8000) or by return email, and delete 
the e-mail and do not disclose its contents to any person.  We believe, but do
not warrant, that this e-mail and any attachments are virus free, but you must
take full responsibility for virus checking. Please refer to 
http://www.dresdnerkleinwort.com/disc/email/ and read our e-mail disclaimer 
statement and monitoring policy.

Dresdner Kleinwort is a brand and trading name of the Commerzbank group and 
operates through Commerzbank AG, Dresdner Kleinwort Limited and their affiliated
or associated companies.  Commerzbank AG is a company incorporated in Germany
with limited liability and registered in England (registered no. FC008139, place
of business 60 Gracechurch Street, London EC3V 0HR) and is authorised by 
Bundesanstalt fuer Finanzdienstleistungsaufsicht (BaFin) and authorised and 
subject to limited regulation by the Financial Services Authority (FSA).
Dresdner Kleinwort Limited is a company incorporated in England with limited 
liability (registered no. 551334, registered office 30 Gresham Street, London 
EC2V 7PG) and is authorised and regulated by the FSA.  Details about the extent
of our authorisations and regulation are available on request. 

Mogwai ERDesigner NG is a Java based entity releationship design
tool. It includes the following key features:

* is based on Java and can be run on Windows and Unix systems
* has a powerful WYSIWYG for physical database design
* handles tables, relations, indexes and comments
* supports a central repository for all models ( Model Repository )
* supports subject areas
* supports domains
* supports MySQL, Oracle, DB2(experimental), Microsoft SQLServer,
PostgreSQL and H2
* creates the SQL DDL statements for schema creation
* has an integrated schema version control system
* can generate schema migration scripts for every change
* stores the database definition as XML files for further processing
* can export the database schema as GIF, BMP, JPEG or SVG files
* has an integrated reverse engineering module for existing schemas
* has a build in schema compare feature
* can generate schema documentation as PDF, HTML, RTF and other
formats
* supports schema conversion between different dialects
* it is based on GPL license
* support is available by authors and newsgroups

Also, ERDesignerNG is available as a SQuirreL SQL and as a NetBeans
Plugin. There is also a new feature for OpenXava application skeleton
generation for the loaded database model.

The 1.7-SNAPSHOT release includes the following changes:

* Improved UI response during long time tasks like reverse engineering
and complete compare
* Added support for automatic IZPack installers
* Improved handling of recently used files and last database
connections
* Added support for H2 (Thanks to Thomas Breitkreuz)
* Improved complete compare functionality for indexes
* If there is a duplicate relation name during reverse engineering, a
new unique name is generated
* Added support to Export model to OpenXava
* Bug Fixing 2513135 [ERDesignerNG] Oracle complete compare fails with
date colum
* Bug Fixing 2675526 [ERDesignerNG] Generation of migration script not
possible
* Bug Fixing 2615849 [ERDesignerNG] Wrong dialect is used to
communicate with rep
* Bug Fixing 2504309 [ERDesignerNG] ERdesigner 1.6: problems on exit
* Bug Fixing 2675509 [ERDesignerNG] Oracle RE of indexes fails
* Bug Fixing 2616079 [ERDesignerNG] OnUpdate=Cascade not persisted
* Bug Fixing 2675551 [ERDesignerNG] DB model comparison does not work
* Bug Fixing 2675559 [ERDesignerNG] Clipping labels
* Bug Fixing 2686597 [ERDesignerNG] Used domains are deletable
* Bug Fixing 2686630 [ERDesignerNG] Default value not setable
* Bug Fixing 2686882 [ERDesignerNG] Domains not initialized
* Bug Fixing 2686627 [ERDesignerNG] 'NOT NULL' ist not generated
* Bug Fixing 2675535 [ERDesignerNG] Not possible to edit relations in
subject area
* Bug Fixing 2292224 [ERDesignerNG] Comments cannot be added to
Subject Areas
* Bug Fixing 2735418 [ERDesignerNG] Table content is clipped
* Bug Fixing 2735413 [ERDesignerNG] German umlauts corrupted
* Implemented FR 2581994 [ERDesignerNG] Support for function based
indexes
* Implemented FR 1905364 [ERDesignerNG] Add support for views ( early
alpha )
* Implemented FR 2675641 [ERDesignerNG] ESC Default buttons for
dialogs
* Implemented FR 2686903 [ERDesignerNG] Store main window size
* Implemented FR 2675574 [ERDesignerNG] Resizable dialog windows
* Implemented FR 1889667 [ERDesignerNG] Allow editing of Edge
Waypoints ( right click + ALT )
* Implemented FR 2686546 [ERDesignerNG] Save vs. Save As
* Implemented FR 2169348 [ERDesignerNG] Allow switching of database/
dialect to generated mult. ddls
* Implemented FR 2690714 [ERDesignerNG] Add relation constraint
RESTRICT
* Implemented FR 2714523 [ERDesignerNG] prompt for password before db
operation
* Implemented FR 2504332 [ERDesignerNG] better comments display
* Implemented FR 2711884 [ERDesignerNG] Add support for hidden
relationships
* Implemented FR 2686547 [ERDesignerNG] Export to HTML
* Implemented FR 2220184 [ERDesignerNG] Make documentation available
as JavaHelp
* Implemented FR 2690710 [ERDesignerNG] Start script should switch to
installation directory
* Implemented FR 2725418 [ERDesignerNG] Add support for custom types

Feel free to visit the projects website at
http://mogwai.sourceforge.net for more details.

Regards

Mirko Sertic
Project admin
 

Hi everyone,

I¹ve been running into a problem with stored procedures which return
multiple results sets when there are updates between each select statement.
On at least MS SQL Server, Sybase ASE and Sybase IQ (I¹ve tested on these
three platforms) the following stored proc should return two results sets
however Squirrel is missing out the second set.

drop procedure nprTest;
create procedure nprTest as
    begin
    create table #tmp1 (tmpCol int)
    insert into #tmp1 values(1)
    select count(*) from #tmp1
    insert into #tmp1 values(2)
    select count(*) from #tmp1
    end;
exec nprTest;

Note it is the existence of the insert between the two select statements
which is causing this to happen ­ two sets are displayed if the insert is
missing.

The error seems to be in processQuery in
net.sourceforge.squirrel_sql.client.session.SQLExecuterTask ­ the notes in
the source indicate this has been problematic in the past, and indeed there
are significant changes from the code I originally contributed for
v1.2beta5...... Having had a quick glance the purpose of some of the current
code is not clear to me.

So before I try and work out a good solution to this, anyone else have any
opinions or test cases which the existing code is supposed to work around ?

Thanks,

Neville
This e-mail is confidential and the information contained in it may be
privileged. It should not be read, copied or used by anyone other than the
intended recipient.  If you have received it in error, please contact the sender
immediately by telephoning (+44 (0)20 7623 8000) or by return email, and delete 
the e-mail and do not disclose its contents to any person.  We believe, but do
not warrant, that this e-mail and any attachments are virus free, but you must
take full responsibility for virus checking. Please refer to 
http://www.dresdnerkleinwort.com/disc/email/ and read our e-mail disclaimer 
statement and monitoring policy.

Dresdner Kleinwort is a brand and trading name of the Commerzbank group and 
operates through Commerzbank AG, Dresdner Kleinwort Limited and their affiliated
or associated companies.  Commerzbank AG is a company incorporated in Germany
with limited liability and registered in England (registered no. FC008139, place
of business 60 Gracechurch Street, London EC3V 0HR) and is authorised by 
Bundesanstalt fuer Finanzdienstleistungsaufsicht (BaFin) and authorised and 
subject to limited regulation by the Financial Services Authority (FSA).
Dresdner Kleinwort Limited is a company incorporated in England with limited 
liability (registered no. 551334, registered office 30 Gresham Street, London 
EC2V 7PG) and is authorised and regulated by the FSA.  Details about the extent
of our authorisations and regulation are available on request. 

Developers,

Since the early days of SQuirreL in 2001, two tools have been used to
develop the code - namely Ant and CVS.  We are currently reviewing the
benefits that Maven2 and Subversion would afford this project and
wanted to give everyone an idea of what to expect in the coming
months.  I must admit that I was a doubter when I first began to use
Maven2 and Subversion at my day job over a year ago now.  But in the
time since then, I have gained an appreciation for both of them and
seen their adoption lead to great strides in improved productivity
through integration with other tools.  The key features that I see
SQuirreL benefiting from are:

Subversion:
 1. Ease of resource (file and directory) relocation without loss of
history (essential to help re-arrange our current source tree to
conform to Maven2 convention)
 2. Integration with Trac (project management) which is hosted on
SourceForge and to which we have already opted to use for our wiki.
 3. Ability to easily identify all files that were changed in a given changeset.

Maven:
 1. Dependency declaration: we can declare all of our dependencies in
one place (pom.xml file(s)) instead of in build.xml and the IDE (e.g.
.classpath in Eclipse), for all IDEs that support maven.
 2. Build Plugin Dependency bootstrapping: we can resolve dependencies
on build plugins (e.g. emma, findbugs, pmd) automatically.  This
eliminates the need for the developer to first download
special-purpose build task jars and place them in ANT_HOME/lib (for
example, findbugs Ant task jar).
 3. We can simplify the build scripts by taking advantage of Maven's
convention over configuration (for example - no need to state where
output directories and artifacts are placed).
 4. We can use maven plugins (like assembly, release, IzPack) to
eliminate the need for our special-purpose release ant build script
(build-weekly.xml)
 5. With the M2Eclipse plugin, importing projects into Eclipse is super-easy.
 6. We can create a project archetype that can be used to generate an
example plugin project that eases the setup burden on new developers
(i.e. no need to checkout the entire codebase, and no need to modify
other ant build scripts to build it)
 7. Maven can generate an alternate simple project website with links
to source code, javadocs, bug tracking, mailing lists, projects
reports (unit test, code coverage, findbugs, pmd, etc.)

Here is an outline of what I believe needs to happen in chronological order:

1. Get a fresh checkout from CVS, restructure code to conform to Maven
conventions, write pom files, and test build using Maven to ensure
equivalence with current Ant build.
2. Migrate from SourceForge CVS to SourceForge Subversion using
cvs2svn (http://cvs2svn.tigris.org/) - keep exactly what we have today
except hosted in Subversion; same project structure, still using Ant.
3. Checkout from Subversion and test Ant build scripts to ensure all
resources were migrated properly to Subversion.
4. Create tag in Subversion.
5. Restructure source files to conform to Maven2 hierarchical
structure (i.e. src/main/java/, src/main/resources, src/test/java,
etc.), just like what was done in step 1.
6. Place project poms from prototype (step 1) into fw, app and all
plugin modules.
7. Test build using Maven and commit changes. (At this point we are no
longer using CVS nor Ant).

I'd like to get feedback from developers - especially those with prior
experience migrating from Ant to Maven.  Let me know if you have
suggestions or concerns.  I'll update this thread periodically as
progress is made toward the final goal.

Rob

Chris,

I am not aware of any further efforts from Joe McDonald on this issue.
I read in the DB2 LUW to iSeries porting guide (attached) that most
interfaces allow you to specify naming property as "system" or "sql", so I
suppose the driver allows for this as well - although I have no access
to an iSeries system to confirm this.  I would guess that a simple
work-around could be to specify "sql" as the value for the "naming"
driver property - correct?  In any case, the SQL code in the
plugin assumes the "." is the qualifier separator, which works great on
LUW DB2 but not so much on iSeries.  The trick to making this work
automatically in both platforms - based on session - would be to find
a JDBC API that exposes the naming setting, or at least the character
to be used in qualified names.  I also read that leaving off the schema
qualifier prefix would cause DB2 to search through all it's catalogs for
the object, but this doesn't seem to be a very efficient approach.  So,
without a test system to try out my ideas, I am a bit limited in how I
can help.  You could help by doing some digging to determine a
reliable way to determine naming value ("system" or "sql").  For
example, can this be inferred from the driver property.  What if the
driver property isn't specified ? (that is, is there a default on all iSeries
systems or is that also configurable).  In the worst case, the plugin
could be modified to catch an exception for "." and try "/" instead -
though that is kind of ugly.

Rob

On Wed, May 27, 2009 at 3:30 PM,  <Chr...@sh...> wrote:
>
> Hello Robert,
>
> I've just discovered squirrel sql and the db2 driver you've written...  I
> really want to use this tool and move away from the green screen tools that
> are in use at my company.  I'm having trouble though -- it seems that the
> folks around here are using "system" naming instead of "sql" naming.  I
> found this article on the web:
>
> http://markmail.org/message/il4lnmefesp7uhqv#query:squirrel%20sql%20system%20naming+page:1+mid:xn3sy4ogdjnkv7st+state:results
>
> Where you apparently were talking to another guy about the same thing.  I
> was wondering -- this was a year ago, has any progress been made?  Do you
> have any suggestions that I might try?
>
> Thanks in advance for your help!
>
> Christopher Fury
> Shenandoah Life Insurance Company
>
> ****************************************************************************************
> This message may contain confidential information. If it has been sent to
> you in error,
> please reply to advise the sender of the error and then immediately delete
> this message.
> ****************************************************************************************
>

Andreas,

Trac is a great project collaboration tool, but it doesn't support
integration with CVS - only SVN.  I was once an opponent to switching
to SVN as the integration with Eclipse (via subclipse) was very buggy.
 However, I've been using Eclipse and SVN for a while now in other
projects, and it seems subclipse has improved greatly (not perfect,
but definitely not a liability anymore).  So, I would be in favor of
switching to SVN now.  I'm not sure if everyone else shares that
sentiment.

Rob

On 5/20/09, CptBlaubaer <cpt...@gm...> wrote:
> Hi Rob,
>
> just had a look at the trac based wiki and got the error message
>
> "Warning: Can't synchronize with the repository
> (/nfs/sf-svn/s/sq/squirrel-sql does not appear to be a Subversion
> repository.). Look in the
> Trac log for more information"
>
> Do I lack access-right?
>
> Take care
>
> Andreas
>
> 2009/5/14 Robert Manning <rob...@gm...>
>
> > Yes, we are lagging on wiki-fying our docs.  We have a new trac wiki setup
> here:
> >
> > https://apps.sourceforge.net/trac/squirrel-sql/
> >
> > My plan is to migrate our other wiki documentation pages from our
> > older wiki (http://squirrel-sql.wiki.sourceforge.net/) to
> the trac
> > wiki.
> >
> > Feel free to use either one.  I think they allow logged-in regular
> > non-developer SF users to edit, but let me know if it is a problem.
> >
> > Rob
> >
> >
> >
> >
> > On Wed, May 13, 2009 at 5:11 PM, CptBlaubaer <cpt...@gm...>
> wrote:
> > > Hi Robert, Gerd and all the other makers of SQuirreL,
> > >
> > > perhaps I missed some stuff in the documentation, but I guess setting up
> a
> > > Wiki for examples of installing of drivers and creation of aliases. I
> > > volunteer to write some stuff about Oracle and MySQL, perhaps there are
> some
> > > other people that would provide some info about other databases.
> > >
> > > Keep up the great work on this fantastic database tool.
> > >
> > > Take care
> > >
> > > Andreas
> > >
> ------------------------------------------------------------------------------
> > > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> > > production scanning environment may not be a perfect world - but thanks
> to
> > > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
> > > i700
> > > Series Scanner you'll get full speed at 300 dpi even with all image
> > > processing features enabled. http://p.sf.net/sfu/kodak-com
> > > _______________________________________________
> > > Squirrel-sql-users mailing list
> > > Squ...@li...
> > >
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
> > >
> > >
> >
>
>

hi.
I've removed the directory C:\Documents and
Settings\<user-home>\.squirrel-sql
then restart squirrelSql, it runs OK now.
I checked that it's set Tiny LAF
thanks lot.
On Fri, May 15, 2009 at 19:30, Robert Manning <rob...@gm...>wrote:

> I was able to reproduce NPEs from other Swing UI components after
> switching to the Tiny LAF without restarting SQuirreL - just merely
> using it.  But when I restarted it, I saw no more exceptions after
> that.  Did you switch to Tiny LAF before installing 3.0.1 (say when
> running version 2.x), or did you switch after installing 3.0.1?  If
> you restart SQuirreL or switch to a different LAF, does the problem
> still occur ?
>
> Rob
>
> On Fri, May 15, 2009 at 3:15 PM, Charles Souza <cha...@gm...>
> wrote:
> >  HI,
> > I tried to run the last SQuirreL version. and got this exception. anyone
> > know about this?
> >
> >
> >
> > C:\Arquivos de programas\SQuirreL SQL Client>java -jar squirrel-sql.jar
> > TinyLaF v1.3.04
> > 'Default.theme' not found - using YQ default theme.
> > Exception in thread "main" java.lang.reflect.InvocationTargetException
> >        at java.awt.EventQueue.invokeAndWait(Unknown Source)
> >        at javax.swing.SwingUtilities.invokeAndWait(Unknown Source)
> >        at
> > net.sourceforge.squirrel_sql.fw.gui.GUIUtils.processOnSwingEventThrea
> > d(GUIUtils.java:350)
> >        at
> > net.sourceforge.squirrel_sql.client.gui.WindowManager.<init>(WindowMa
> > nager.java:161)
> >        at
> > net.sourceforge.squirrel_sql.client.Application.executeStartupTasks(A
> > pplication.java:753)
> >        at
> > net.sourceforge.squirrel_sql.client.Application.startup(Application.j
> > ava:246)
> >        at net.sourceforge.squirrel_sql.client.Main.main(Main.java:60)
> > Caused by: java.lang.RuntimeException: java.lang.NullPointerException
> >        at
> > net.sourceforge.squirrel_sql.client.gui.db.JTreeAliasesListImpl.initT
> > ree(JTreeAliasesListImpl.java:233)
> >        at
> > net.sourceforge.squirrel_sql.client.gui.db.JTreeAliasesListImpl.<init
> >>(JTreeAliasesListImpl.java:101)
> >        at
> > net.sourceforge.squirrel_sql.client.gui.db.AliasesList.<init>(Aliases
> > List.java:44)
> >        at
> > net.sourceforge.squirrel_sql.client.gui.WindowManager.createAliasesLi
> > stUI(WindowManager.java:877)
> >        at
> > net.sourceforge.squirrel_sql.client.gui.WindowManager.initialize(Wind
> > owManager.java:861)
> >        at
> > net.sourceforge.squirrel_sql.client.gui.WindowManager.access$200(Wind
> > owManager.java:77)
> >        at
> > net.sourceforge.squirrel_sql.client.gui.WindowManager$1.run(WindowMan
> > ager.java:165)
> >        at java.awt.event.InvocationEvent.dispatch(Unknown Source)
> >        at java.awt.EventQueue.dispatchEvent(Unknown Source)
> >        at
> > net.sourceforge.squirrel_sql.client.Application$1.dispatchEvent(Appli
> > cation.java:195)
> >        at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown
> > Source)
> >        at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown
> Source)
> >        at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
> > Source)
> >        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> >        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> >        at java.awt.EventDispatchThread.run(Unknown Source)
> > Caused by: java.lang.NullPointerException
> >        at
> > net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
> > java:149)
> >        at
> > net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
> > java:110)
> >        at
> > net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
> > java:87)
> >        at
> > net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
> > java:77)
> >        at
> > net.sourceforge.squirrel_sql.client.gui.db.JTreeAliasesListImpl.initT
> > ree(JTreeAliasesListImpl.java:217)
> >        ... 15 more
> > Caused by: java.lang.NullPointerException
> >        at
> > net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
> > java:137)
> >        ... 19 more
> >
> > C:\Arquivos de programas\SQuirreL SQL Client>
> >
> >
> > --
> > Charles Danilo de Souza
> >
> ------------------------------------------------------------------------------
> > Crystal Reports - New Free Runtime and 30 Day Trial
> > Check out the new simplified licensing option that enables
> > unlimited royalty-free distribution of the report engine
> > for externally facing server and web deployment.
> > http://p.sf.net/sfu/businessobjects
> > _______________________________________________
> > Squirrel-sql-develop mailing list
> > Squ...@li...
> > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> >
>



-- 
Charles Danilo de Souza

I was able to reproduce NPEs from other Swing UI components after
switching to the Tiny LAF without restarting SQuirreL - just merely
using it.  But when I restarted it, I saw no more exceptions after
that.  Did you switch to Tiny LAF before installing 3.0.1 (say when
running version 2.x), or did you switch after installing 3.0.1?  If
you restart SQuirreL or switch to a different LAF, does the problem
still occur ?

Rob

On Fri, May 15, 2009 at 3:15 PM, Charles Souza <cha...@gm...> wrote:
>  HI,
> I tried to run the last SQuirreL version. and got this exception. anyone
> know about this?
>
>
>
> C:\Arquivos de programas\SQuirreL SQL Client>java -jar squirrel-sql.jar
> TinyLaF v1.3.04
> 'Default.theme' not found - using YQ default theme.
> Exception in thread "main" java.lang.reflect.InvocationTargetException
>        at java.awt.EventQueue.invokeAndWait(Unknown Source)
>        at javax.swing.SwingUtilities.invokeAndWait(Unknown Source)
>        at
> net.sourceforge.squirrel_sql.fw.gui.GUIUtils.processOnSwingEventThrea
> d(GUIUtils.java:350)
>        at
> net.sourceforge.squirrel_sql.client.gui.WindowManager.<init>(WindowMa
> nager.java:161)
>        at
> net.sourceforge.squirrel_sql.client.Application.executeStartupTasks(A
> pplication.java:753)
>        at
> net.sourceforge.squirrel_sql.client.Application.startup(Application.j
> ava:246)
>        at net.sourceforge.squirrel_sql.client.Main.main(Main.java:60)
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException
>        at
> net.sourceforge.squirrel_sql.client.gui.db.JTreeAliasesListImpl.initT
> ree(JTreeAliasesListImpl.java:233)
>        at
> net.sourceforge.squirrel_sql.client.gui.db.JTreeAliasesListImpl.<init
>>(JTreeAliasesListImpl.java:101)
>        at
> net.sourceforge.squirrel_sql.client.gui.db.AliasesList.<init>(Aliases
> List.java:44)
>        at
> net.sourceforge.squirrel_sql.client.gui.WindowManager.createAliasesLi
> stUI(WindowManager.java:877)
>        at
> net.sourceforge.squirrel_sql.client.gui.WindowManager.initialize(Wind
> owManager.java:861)
>        at
> net.sourceforge.squirrel_sql.client.gui.WindowManager.access$200(Wind
> owManager.java:77)
>        at
> net.sourceforge.squirrel_sql.client.gui.WindowManager$1.run(WindowMan
> ager.java:165)
>        at java.awt.event.InvocationEvent.dispatch(Unknown Source)
>        at java.awt.EventQueue.dispatchEvent(Unknown Source)
>        at
> net.sourceforge.squirrel_sql.client.Application$1.dispatchEvent(Appli
> cation.java:195)
>        at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown
> Source)
>        at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
>        at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
> Source)
>        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
>        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
>        at java.awt.EventDispatchThread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
>        at
> net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
> java:149)
>        at
> net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
> java:110)
>        at
> net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
> java:87)
>        at
> net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
> java:77)
>        at
> net.sourceforge.squirrel_sql.client.gui.db.JTreeAliasesListImpl.initT
> ree(JTreeAliasesListImpl.java:217)
>        ... 15 more
> Caused by: java.lang.NullPointerException
>        at
> net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
> java:137)
>        ... 19 more
>
> C:\Arquivos de programas\SQuirreL SQL Client>
>
>
> --
> Charles Danilo de Souza
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited royalty-free distribution of the report engine
> for externally facing server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>

 HI,
I tried to run the last SQuirreL version. and got this exception. anyone
know about this?



C:\Arquivos de programas\SQuirreL SQL Client>java -jar squirrel-sql.jar
TinyLaF v1.3.04
'Default.theme' not found - using YQ default theme.
Exception in thread "main" java.lang.reflect.InvocationTargetException
        at java.awt.EventQueue.invokeAndWait(Unknown Source)
        at javax.swing.SwingUtilities.invokeAndWait(Unknown Source)
        at
net.sourceforge.squirrel_sql.fw.gui.GUIUtils.processOnSwingEventThrea
d(GUIUtils.java:350)
        at
net.sourceforge.squirrel_sql.client.gui.WindowManager.<init>(WindowMa
nager.java:161)
        at
net.sourceforge.squirrel_sql.client.Application.executeStartupTasks(A
pplication.java:753)
        at
net.sourceforge.squirrel_sql.client.Application.startup(Application.j
ava:246)
        at net.sourceforge.squirrel_sql.client.Main.main(Main.java:60)
Caused by: java.lang.RuntimeException: java.lang.NullPointerException
        at
net.sourceforge.squirrel_sql.client.gui.db.JTreeAliasesListImpl.initT
ree(JTreeAliasesListImpl.java:233)
        at
net.sourceforge.squirrel_sql.client.gui.db.JTreeAliasesListImpl.<init
>(JTreeAliasesListImpl.java:101)
        at
net.sourceforge.squirrel_sql.client.gui.db.AliasesList.<init>(Aliases
List.java:44)
        at
net.sourceforge.squirrel_sql.client.gui.WindowManager.createAliasesLi
stUI(WindowManager.java:877)
        at
net.sourceforge.squirrel_sql.client.gui.WindowManager.initialize(Wind
owManager.java:861)
        at
net.sourceforge.squirrel_sql.client.gui.WindowManager.access$200(Wind
owManager.java:77)
        at
net.sourceforge.squirrel_sql.client.gui.WindowManager$1.run(WindowMan
ager.java:165)
        at java.awt.event.InvocationEvent.dispatch(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Unknown Source)
        at
net.sourceforge.squirrel_sql.client.Application$1.dispatchEvent(Appli
cation.java:195)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown
Source)
        at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.lang.NullPointerException
        at
net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
java:149)
        at
net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
java:110)
        at
net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
java:87)
        at
net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
java:77)
        at
net.sourceforge.squirrel_sql.client.gui.db.JTreeAliasesListImpl.initT
ree(JTreeAliasesListImpl.java:217)
        ... 15 more
Caused by: java.lang.NullPointerException
        at
net.sourceforge.squirrel_sql.fw.xml.XMLBeanReader.load(XMLBeanReader.
java:137)
        ... 19 more

C:\Arquivos de programas\SQuirreL SQL Client>


-- 
Charles Danilo de Souza

Johan,

The update manager ensures that plugins, translations and core
artifacts stay in sync.  We occasionally change APIs in a way which is
not backward-compatible, so using the update manager to get updates
for plugins and translations and not for core artifacts is
problematic.  But it is trivial to modify SQuirreL to disable the
update manager.  Simply comment out or remove line 411 in
net.sourceforge.squirrel_sql.client.gui.mainframe.MainFramMenuBar.java
:

addToMenu(rsrc, UpdateAction.class, menu);

With this line commented out or removed, the user has no way to access
the update manager feature as it will no longer be included in the
Help menu.

Rob

On Thu, Apr 23, 2009 at 1:20 PM, Johan Brelet <joh...@gm...> wrote:
> Hello,
>
> I'm currently developing a custom SQuirreL application for a client.
> Unfortunately I canno't give it to the community because it deals with
> security (password encryption...)
>
> As I updated the core part of SQuirreL, I need to disable Software Update
> Manager so as potential users cannot choose to update their application
> (which has the effect to overwrite my custom version!).
> So is there a simple and non intrusive way to remove it? or to restrict it
> to plugins and translations only?
>
> Regards,
>
> Johan
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>

Joe,

Yes - I started to write a diff plugin, but never finished. It
provides basic table differences in a JTable dialog and works like the
DBCopy plugin where you select a table to compare using the context
menu (right-click) and then select another table to compare it to in a
different session.  I never completed it and so I didn't include it in
the installer.  There was one other person who expressed interest in
completing it, but I haven't heard from that person in a while and I
don't believe he got very far.  The code is here:

http://squirrel-sql.cvs.sourceforge.net/viewvc/squirrel-sql/sql12/plugins/dbdiff/

Patch submissions are welcomed.

Rob

On Thu, Apr 23, 2009 at 11:57 AM, Joe Rochette <joe...@gm...> wrote:
> I think I want to try to start building a plugin:
>
> Has anyone put any thought into the best way to create a "Diff Tool" ?
>
> Before I switched from data studio i used this quite a bit;  Basically it
> would extract DDL from two hosts into the client side, and then create a
> chart displaying objects that have differences/etc.
>
> Lately I've just been trying to script things to extract a bunch of DDL into
> a directory, then using vimdiff to look at the differences.  Its not quite
> as convienennt but its been getting the job done.
>
> What do you guys think?
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>

Hello,

I'm currently developing a custom SQuirreL application for a client.
Unfortunately I canno't give it to the community because it deals with
security (password encryption...)

As I updated the core part of SQuirreL, I need to disable Software Update
Manager so as potential users cannot choose to update their application
(which has the effect to overwrite my custom version!).
So is there a simple and non intrusive way to remove it? or to restrict it
to plugins and translations only?

Regards,

Johan

I think I want to try to start building a plugin:

Has anyone put any thought into the best way to create a "Diff Tool" ?

Before I switched from data studio i used this quite a bit;  Basically it
would extract DDL from two hosts into the client side, and then create a
chart displaying objects that have differences/etc.

Lately I've just been trying to script things to extract a bunch of DDL into
a directory, then using vimdiff to look at the differences.  Its not quite
as convienennt but its been getting the job done.

What do you guys think?

Wumo.. Its probably best to just jump in and try to understand the code. For
instance, you can try checking out some base classes and see how they relate
to each other. Check out a small bug, and see if you can at least determine
where its happening, if not how to fix it.

In other words, just do it!

Johnathan (another new Squirrel user)

On Sun, Apr 19, 2009 at 9:17 PM, Wumo Pan <wum...@ce...>wrote:

> Hi,
>
> I'm a biginner to Squirrel SQL and I'm willing to study the source code
> of this project. Any suggestion as where to start with?
>
> Many thanks.
> Wumo
>
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>

Hi,

I'm a biginner to Squirrel SQL and I'm willing to study the source code 
of this project. Any suggestion as where to start with?

Many thanks.
Wumo

It sounds like it would be a great addition to the Oracle plugin.  You
can submit it as a patch here:

https://sourceforge.net/tracker/?group_id=28383&atid=393416

Rob

On Thu, Apr 16, 2009 at 7:38 AM, David Moreno
<jos...@ya...> wrote:
>
> Hi,
> I have written a small plugin to generate Oracle SQL*Loader control files for selected tables.
> I would like to know your opinion about whether it may be interesting to make the plugin publicly available (in your site or elsewhere).
> Regards.
>
>
>
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>

Hi,
I have written a small plugin to generate Oracle SQL*Loader control files for selected tables.
I would like to know your opinion about whether it may be interesting to make the plugin publicly available (in your site or elsewhere).
Regards.



      

Thank you for helping to improve SQuirreL !  We've added this to the
repository and attributed the work to you.  You can send us an updated
jar whenever you like.

Rob

On Tue, Mar 10, 2009 at 9:34 PM, 김영우 <war...@gm...> wrote:
> Hi Folks,
>
> I'm Youngwoo Kim. It seems that my first email was not deliverd properly so
> I re-send my email.
> I am really appreciative of all developers and contributors. SQuirreL makes
> my work much easier. It's very useful for me. :-)
>
> I've been translating the messages into Korean(ko_KR). please check out,
> http://mixellaneous.tistory.com/attachment/cfi...@14...
> The jar file name sould be 'squirrel_sql_ko_KR.jar'. It's incomplete but
> important messages are done, and I'll translate rest of the messages ASAP.
>
> Regards,
>
> Youngwoo
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Squirrel-sql-translators mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-translators
>
>

That is a good start.  Those 3 properties should get their own section
in the session props panel, and they should be disabled when a plugin
registers a custom tokenizer.  Also, a red label above them in that
section should indicate that these properties cannot be configured
here, but they can be in the Global Preferences Sheet tab for that
session's plugin.


Rob


On Tue, Mar 10, 2009 at 5:22 PM, Gerd Wagner <ger...@t-...> wrote:
>
> I think I understand what you mean. Probably moving the tabs in "New Session
> Properies" to our Alias properties would come quite close to what you are
> saying. I see that this would be the most correct from a logical point of
> view. But I believe that users wouldn't appreciate this much of
> configuration. If that is true a compromise is needed and I suggest the
> following:
>
> If a custom query tokenizer exists we should disable editing of
> - statement separator
> - start of line comment
> - remove multi-line comments
> (or at least those of the three that are predefined by the custom tokenizer)
> set them as well as we can on base of the custom query tokenizer and tell
> the user that they were set by a plugin.
>
> That is a compromise but it makes things quite clear for users and is rather
> easy to implement. It clearly doesn't solve discrepancy between "New Session
> Properies" and custom tokenizers.
>
>
> Would that be OK?
>
>
> Gerd
>

Robert Manning wrote:
> Gerd,
> 
> I agree that it is not ideal that these three properties (statement
> separator / start of line comment / remove multi-line comments) are
> displayed in the session properties as well as the plugin preferences
> sheet (each plugin that defines a custom querytokenizer provides these
> settings in that plugins preferences sheet).  And beyond that, it is
> also not ideal that changing the session properties sheet doesn't
> affect the custom query tokenizer's settings.  Perhaps a compromise
> would be to apply the settings in session properties to a session's
> query tokenizer. The main trouble that I see with this is that custom
> tokenizer's are specific to a type of session (one with a plugin that
> registers a custom tokenizer).  But "New Session Properties" applies
> globally to all "new" sessions, regardless of type.
> 
> I would like to illustrate this problem with an example. Suppose you
> have three different aliases (Sybase, Oracle and Ingres).  Now, you
> also probably have installed the Sybase plugin, the Oracle plugin and
> no plugin for Ingres (we don't have one).  New Session Properties only
> applies to the Ingres sessions, because the other two types of
> sessions have a plugin which registers it's own tokenizer and keeps
> it's own property values for the 3 properties (statement separator /
> start of line comment / remove multi-line comments) and stored
> procedure/function separator.  The statement separator is the chief
> culprit in making configuration a challenge for SQuirreL.  On Oracle
> it should be ";" for regular SQL statements and <eol> / <eol> for
> stored procedures, functions and anonymous blocks.  On Sybase, it
> should be <eol> GO <eol> or  <eol> go <eol> for all statement types.
> For ingres, it is whatever you want, but probably ";" for regular
> statements and go pick a character if you want to program stored
> procedures - your life is not so easy with Ingres because it doesn't
> have a plugin and therefore doesn't install a custom tokenizer where
> you can keep settings for all of your scripts that make them work.
> So, given the above setup, suppose a user launches squirrel and
> accesses the "New Session Properties" dialog and configures ";" for
> statement separator.  Which session type(s) should this setting apply
> to ? What will SQuirreL do to correctly parse stored procedures ?
> 
> I have to confess here, that I've never been a big fan of the dualism
> we have for session properties (New Session Properties vs. This
> Session's Properties) because it leads people again and again to
> configure "This Session's Properties" and they think that the change
> persists - that is until they launch a new session find out that it
> doesn't.  If we were going to make a change in favor of transparency,
> I'd like to see if somehow we could eliminate "New Session Properties"
> and have the "session properties" dialog be always persisted.  I
> suspect that we only needed a temporary "session-only" configuration
> simply to support session deviation on the statement separator.  Now
> that we can provide much better support for properly parsing most
> db-specific SQL that you are likely to want to run in SQuirreL, I
> don't see the great necessity for "temporary session-only" properties.
>  Perhaps if we eliminate this distinction, we could also allow the
> session properties to be populated from the custom tokenizer and also
> write them back to the plugin preferences from the session properties
> dialog.  Going one step further would be to provide a plugin API to
> allow custom session-specific properties to be registered in the
> session properties dialog itself, potentially eliminating the need for
> plugin preferences sheets altogether.
> 
> Sorry for the long email, I hope it is clear and let me know your thoughts.

I think I understand what you mean. Probably moving the tabs in "New Session 
Properies" to our Alias properties would come quite close to what you are 
saying. I see that this would be the most correct from a logical point of view. 
But I believe that users wouldn't appreciate this much of configuration. If that 
is true a compromise is needed and I suggest the following:

If a custom query tokenizer exists we should disable editing of
- statement separator
- start of line comment
- remove multi-line comments
(or at least those of the three that are predefined by the custom tokenizer) set 
them as well as we can on base of the custom query tokenizer and tell the user 
that they were set by a plugin.

That is a compromise but it makes things quite clear for users and is rather 
easy to implement. It clearly doesn't solve discrepancy between "New Session 
Properies" and custom tokenizers.


Would that be OK?


Gerd

Gerd,

I agree that it is not ideal that these three properties (statement
separator / start of line comment / remove multi-line comments) are
displayed in the session properties as well as the plugin preferences
sheet (each plugin that defines a custom querytokenizer provides these
settings in that plugins preferences sheet).  And beyond that, it is
also not ideal that changing the session properties sheet doesn't
affect the custom query tokenizer's settings.  Perhaps a compromise
would be to apply the settings in session properties to a session's
query tokenizer. The main trouble that I see with this is that custom
tokenizer's are specific to a type of session (one with a plugin that
registers a custom tokenizer).  But "New Session Properties" applies
globally to all "new" sessions, regardless of type.

I would like to illustrate this problem with an example. Suppose you
have three different aliases (Sybase, Oracle and Ingres).  Now, you
also probably have installed the Sybase plugin, the Oracle plugin and
no plugin for Ingres (we don't have one).  New Session Properties only
applies to the Ingres sessions, because the other two types of
sessions have a plugin which registers it's own tokenizer and keeps
it's own property values for the 3 properties (statement separator /
start of line comment / remove multi-line comments) and stored
procedure/function separator.  The statement separator is the chief
culprit in making configuration a challenge for SQuirreL.  On Oracle
it should be ";" for regular SQL statements and <eol> / <eol> for
stored procedures, functions and anonymous blocks.  On Sybase, it
should be <eol> GO <eol> or  <eol> go <eol> for all statement types.
For ingres, it is whatever you want, but probably ";" for regular
statements and go pick a character if you want to program stored
procedures - your life is not so easy with Ingres because it doesn't
have a plugin and therefore doesn't install a custom tokenizer where
you can keep settings for all of your scripts that make them work.
So, given the above setup, suppose a user launches squirrel and
accesses the "New Session Properties" dialog and configures ";" for
statement separator.  Which session type(s) should this setting apply
to ? What will SQuirreL do to correctly parse stored procedures ?

I have to confess here, that I've never been a big fan of the dualism
we have for session properties (New Session Properties vs. This
Session's Properties) because it leads people again and again to
configure "This Session's Properties" and they think that the change
persists - that is until they launch a new session find out that it
doesn't.  If we were going to make a change in favor of transparency,
I'd like to see if somehow we could eliminate "New Session Properties"
and have the "session properties" dialog be always persisted.  I
suspect that we only needed a temporary "session-only" configuration
simply to support session deviation on the statement separator.  Now
that we can provide much better support for properly parsing most
db-specific SQL that you are likely to want to run in SQuirreL, I
don't see the great necessity for "temporary session-only" properties.
 Perhaps if we eliminate this distinction, we could also allow the
session properties to be populated from the custom tokenizer and also
write them back to the plugin preferences from the session properties
dialog.  Going one step further would be to provide a plugin API to
allow custom session-specific properties to be registered in the
session properties dialog itself, potentially eliminating the need for
plugin preferences sheets altogether.

Sorry for the long email, I hope it is clear and let me know your thoughts.

Rob


On Sun, Mar 8, 2009 at 12:03 PM, Gerd Wagner <ger...@t-...> wrote:
> Hi all,
>
> finally I make it to come back to the point below.
>
> As far as I understand things now the concept of CustomQueryTokenizers goes
> quite a bit beyond the three simple Session Properties we had before. So
> simply replacing the properties in Session Properties may turn out
> inadequate.
>
> On the other hand I think it is very important that what the user sees and
> what a Plugin programmer uses should be made clear an transparent.
>
> This is to say I suggest we give programmers a unique interface to
> Tokenizers but also find a way to adequately display a custom tokenizers
> configs in our Session Properties. I'm not sure yet how far this has to go.
> The furtherest would be to provide custom tokenizer dependent panels.
>
> At the moment I think it is not such a nice thing that for some RDBMS we
> display  props that aren't actually used.
>
> So far my 2 cents.
>
> Gerd
>
>
> Robert Manning wrote:
>>
>> Gerd,
>>
>> Is it necessary to override the user's preference for "remove
>> multiline comment" in HQLPanelController.onConvertToSQL (line 81) ? :
>>
>>         String statementSeparator =
>> _sess.getProperties().getSQLStatementSeparator();
>>         String startOfLineComment =
>> _sess.getProperties().getStartOfLineComment();
>>         QueryTokenizer qt = new QueryTokenizer(statementSeparator,
>> startOfLineComment, true);
>>         qt.setScriptToTokenize(hql);
>>
>> If it isn't then I'd propose we change the above to:
>>
>>         QueryTokenizer qt = _sess.getQueryTokenizer();
>>         qt.setScriptToTokenize(hql);
>>
>> It would be nice to keep the plugin overrides (via custom
>> QueryTokenizer) without transferring their values
>> to a Session's SessionProperties object.  Less potential confusion and
>> Guido's recent fix in Session would
>> be unnecessary. I would also like to give SessionProperties an
>> interface that removes these methods to
>> users of Session so that they are forced (unless they cast) to use the
>> QueryTokenizer which should be
>> treated as the authority for these properties.  If the override of
>> remove multi-line comment (the "true"
>> parameter above hard-codes remove multi-line comments to on,
>> regardless of what is in session
>> properties) is a hard requirement, then I would propose giving
>> IQueryTokenizer a clone method (or copy
>> constructor) and using that to get a new QueryTokenizer to hard-code
>> the value in.  What are your
>> thoughts on this ?
>>
>> Rob
>>
>
>

Just a heads up: you will need to update your project settings for
fw/lib jars whose version suffix has been stripped off.  I had to do
this because the Update feature currently has a design limitation that
depends on the library jar filename remaining constant in successive
releases.

Rob

Hi folks,

Perhaps you will recall the plans that we made back in December 2008
to release SQuirreL 3.0 at the end of January (see below).  Well, we
have been testing/fixing since then, and we've come to a point where
we feel comfortable that the features we have added to the release are
stable and very usable.  We would like to release 3.0 the weekend of
Feb 21st (not this weekend, but the next).  If anyone has updated
translations to provide it's not too late to do so - just send them to
myself or Gerd and we will see that they are included.  Also, if
anyone would like to give the new release a try, just grab the latest
snapshot and please file a bug report for any issues you encounter.

Rob


---------- Forwarded message ----------
From: Robert Manning <rob...@gm...>
Date: Tue, Dec 23, 2008 at 5:56 AM
Subject: Release planning
To: squ...@li...,
squirrel-sql-develop <squ...@li...>


All,

Gerd and I recently made some decisions about the next major release
of SQuirreL.
(This doesn't apply to 2.6.9 which is a minor release and may be
released soon).
We have been adding enhancements to the trunk which have only been available in
the snapshot builds for the entire year of 2008.  The enhancements involve many
areas of the code and will give SQuirreL a new look as well as new
features.  Also,
some of the UI changes leverage Java APIs that are only available in
Java6.  There
are also enhanced JDBC APIs that will be used going forward that are also only
available in Java6.  We dropped support for 1.4 on 12/31/2006 with the
2.4 release and
moved to Java5 then.  While dropping support for Java5 in this upcoming release
may not be well received by some users, we believe that is the best
way forward for
SQuirreL.   Given that there are so many changes, rather than calling
the next release 2.7,
we decided it would be more appropriate to call the release 3.0.  As
far as timing, we
are currently planning an end of January release date - although that
is not set in stone.
Let us know of any development or translation concerns on the
appropriate mailing
list as soon as you can.

Rob

Konstantin,

Probably you just need to add the appropriate JDBC driver. Is that enough
info to get started?

-Matt

-----Original Message-----
From: Konstantin Krasnov [mailto:kr...@gm...] 
Sent: Thursday, 22 January, 2009 20:40
To: squ...@li...
Subject: [Squirrel-sql-develop] Support for DB2 for z/OS

Hi!

I want to add support for IBM DB2 for z/OS. How can I do this?

P.S.
Sorry for my English.

--
Best regards,
Konstantin Krasnov

--------------------------------------------------------------------------
----
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Hi!

I want to add support for IBM DB2 for z/OS. How can I do this?

P.S.
Sorry for my English.

--
Best regards,
Konstantin Krasnov