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

Hi developers,

my name is Michael Romankiewicz. 
Some years ago, I develop my first db tool like squirell with delphi and their database engine.
Before 4 years I began with a new implementation with java (swing). 
Since this was my first larger Java project, it has naturally some weaknesses.
And thus I had decided to put the project on again new.
Coincidentally I discovered now SQuirreL.
I want to develop the missing parts to my tool here as plugin. 

And so I have some questions to you:

- Is there anyone to program a grant manager?
- Does Roman Rokytskyy is working on his firebird plugin?  I use mainly firebird. 
- I think to develop tools for backup, restore and other server services for the firebird plugin.

And my last question for my poorly english ;-)
Does someone speak of you german?

Many greets
Mike
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066

Forgot to mention - I encourage everyone to sign up for a Wikipedia
account (if you don't have one already) and add to or edit the pages
that are there.  At this point it's just these two:

http://en.wikipedia.org/wiki/SQuirreL_SQL_Client
http://en.wikipedia.org/wiki/SQuirreL_SQL_Client_Plugin_API

Rob

On 6/20/07, Robert Manning <rob...@gm...> wrote:
> I've begun to add some notes to a SQuirreL SQL Plugin API page on
> Wikipedia.  I have some stubs to fill in yet, but I think it's a good
> start.  If anyone would like to provide feedback on it feel free (like
> APIs that are not documented, or inaccuracies in what is there) - the
> page is here:
>
> http://en.wikipedia.org/wiki/SQuirreL_SQL_Client_Plugin_API
>
> Rob
>

I've begun to add some notes to a SQuirreL SQL Plugin API page on
Wikipedia.  I have some stubs to fill in yet, but I think it's a good
start.  If anyone would like to provide feedback on it feel free (like
APIs that are not documented, or inaccuracies in what is there) - the
page is here:

http://en.wikipedia.org/wiki/SQuirreL_SQL_Client_Plugin_API

Rob

On 6/19/07, da...@ce... <da...@ce...> wrote:
> One other (quick, I hope) question. Once a query is run (and a
> corresponding result tab created), what's the API that lets me grab
> hold of the result tab currently selected by the user?

There may be a way to accomplish this in fewer lines of code but I see
only this approach at the moment -

1. When a session starts, save off a reference to the SessionManager:

IApplication application = ISession.getApplication();
SessionManager sessionManager = application.getSessionManager();

2. At some later point when you want to get a reference to the
currently selected result tab do the following:

ISession currentSession = sessionManager.getActiveSession();
SessionInternalFrame sessionInternalFrame =
currentSession.getSessionInternalFrame();
SessionPanel sessionPanel = sessionInternalFrame.getSessionPanel();
SQLPanel sqlPanel = sessionPanel.getSQLPanel();
SQLResultExecuterPanel sqlResultExecuterPanel = sqlPanel.getSQLExecPanel();
ResultTab selectedResultTab = sqlResultExecuterPanel.getSelectedResultTab();


It shouldn't be this difficult, and I also sent this to the list in
case anyone wants to provide additional insight on how to accomplish
what you've asked.

Rob

On 6/19/07, da...@ce... <da...@ce...> wrote:
> Thanks, Rob. The log you sent shows the listener triggering as it
> should. Strangely, I don't see that happen when I run the same code
> here. I'll have to puzzle over that, and over the DialectFactory issue
> (what does DialectFactory do?). I'll continue to look at it.
>

We had an issue with the ISQLExecutionListener API that was resolved
in the last couple of months.  I bet it didn't make it into 2.5.1 -
the version I think you are using.  You should get the latest code
from the trunk and see if that makes a difference.

DialectFactory can give you an extended Hibernate dialect that is
specific to the database
used in the ISession you give it.  Then, there are methods in the
HibernateDialect interface to generate SQL that is specific for that
database.  This is used by DBCopy (mostly for doing type translation),
Refactoring and more recently the SQLScripts plugin for create table
statements.


> One other (quick, I hope) question. Once a query is run (and a
> corresponding result tab created), what's the API that lets me grab
> hold of the result tab currently selected by the user?

ISession
.getSQLPanelAPIOfActiveSessionWindow()
.addResultTabListener(IResultTabListener lis)

IResultTabListener gets events that contain a reference to the
ResultTab just added or removed.  You could use that to keep a
reference to the last one added, although that has problems (like if
the user selects a different one).  We probably need a new API method
here called ISQLPanelAPI.getCurrentResultTab().  I don't see another
way to do it, so I'll take a further look and see if that is
appropriate.

Rob

Hmm.. It looks ok to me.  Any exceptions in the log file?  In the log
file do you see

"Plugin SIMaks created in XX ms"

Rob


On 6/17/07, da...@ce... <da...@ce...> wrote:
> Question from a newbie:
>
> I'm trying to use ISQLExecutionListener. I've created the class shown
> in excerpt 1 below to implement the ISQLExecutionListener interface.
> Then I instantiate this class and pass the instance to
> session.addSQLExecutionListener as shown in excerpt 2 during the
> execution of the sessionStarted callback for my plug-in. Problem is,
> when I then create SQL and execute it in the SQL panel, the listener
> never fires. Any thoughts on where I may be going wrong?
>
> One other question: I need to be able to access result tabs, for
> example to grab selected fields in result tables, and then use this
> information (hopefully) to browse the result dataset model to grab
> other related information. I haven't found any documentation on how to
> get() the currently selected result tab, how to add items to its popup
> menu, or how to get at information inside, like the currently selected
> text. Any help would be greatly appreciated!
>
> Many thanks.
>
> Cheers,
> Dave A.
>
> %%%% start excerpt 1 %%%%%%%%%%%%%%%%%%%%%
>
> package net.sourceforge.squirrel_sql.plugins.simarks;
> import net.sourceforge.squirrel_sql.fw.util.log.ILogger;
> import net.sourceforge.squirrel_sql.fw.util.log.LoggerController;
> import net.sourceforge.squirrel_sql.plugins.simarks.SIMarksPlugin;
>
> public class ISQLExecutionListener implements
>         net.sourceforge.squirrel_sql.client.session.event.ISQLExecutionListener {
>
>         SIMarksPlugin home = null;
>
>      /** Logger for this class. */
>      private final static ILogger log =
>          LoggerController.createLogger(ISQLExecutionListener.class);
>
>      public void statementExecuted(String sql)
>         {
>                 log.info("statementExecuted passed this way");
>                 log.info(sql.toString());
>         }
>
>         public String statementExecuting(String sql)
>         {
>                 home.store_sql(sql);
>                 log.info("SQL Listener triggered: " + home.get_sql().toString());
>                 return null;
>                 // return sql;
>         }
>
>         ISQLExecutionListener() { }
>         ISQLExecutionListener(SIMarksPlugin homebase)
>         {
>                 log.info("SQL Listener established");
>                 home = homebase;
>                 home.store_sql("xxxxx");
>                 log.info(home.get_sql().toString());
>         }
>
>
> }
>
> %%%%% end of excerpt 1 %%%%%%%%%%%%%
>
>
> %%%% start excerpt 2 %%%%%%%%
>
>      public PluginSessionCallback sessionStarted(final ISession session) {
>         final ISQLPanelAPI sqlapi =
> session.getSQLPanelAPIOfActiveSessionWindow();
>
>         final ISQLExecutionListener foo = new ISQLExecutionListener(this);
>         s_log.info("created listener of class " +
> ((ISQLExecutionListener)foo).getClass().toString());
>
>         sqlapi.addSQLExecutionListener((ISQLExecutionListener)foo);
>
>         s_log.info("At init, sql history is: " +
> sqlapi.getSQLHistoryItems().get(0));
>         return new SIMarksPluginSessionCallback(this);
>      }
>
> %%%% end of excerpt 2 %%%%%%%%%%%%
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>

Question from a newbie:

I'm trying to use ISQLExecutionListener. I've created the class shown =20
in excerpt 1 below to implement the ISQLExecutionListener interface. =20
Then I instantiate this class and pass the instance to =20
session.addSQLExecutionListener as shown in excerpt 2 during the =20
execution of the sessionStarted callback for my plug-in. Problem is, =20
when I then create SQL and execute it in the SQL panel, the listener =20
never fires. Any thoughts on where I may be going wrong?

One other question: I need to be able to access result tabs, for =20
example to grab selected fields in result tables, and then use this =20
information (hopefully) to browse the result dataset model to grab =20
other related information. I haven't found any documentation on how to =20
get() the currently selected result tab, how to add items to its popup =20
menu, or how to get at information inside, like the currently selected =20
text. Any help would be greatly appreciated!

Many thanks.

Cheers,
Dave A.

%%%% start excerpt 1 %%%%%%%%%%%%%%%%%%%%%

package net.sourceforge.squirrel_sql.plugins.simarks;
import net.sourceforge.squirrel_sql.fw.util.log.ILogger;
import net.sourceforge.squirrel_sql.fw.util.log.LoggerController;
import net.sourceforge.squirrel_sql.plugins.simarks.SIMarksPlugin;

public class ISQLExecutionListener implements
=09net.sourceforge.squirrel_sql.client.session.event.ISQLExecutionListener {

=09SIMarksPlugin home =3D null;

     /** Logger for this class. */
     private final static ILogger log =3D
         LoggerController.createLogger(ISQLExecutionListener.class);

     public void statementExecuted(String sql)
=09{
=09=09log.info("statementExecuted passed this way");
=09=09log.info(sql.toString());
=09}

=09public String statementExecuting(String sql)
=09{
=09=09home.store_sql(sql);
=09=09log.info("SQL Listener triggered: " + home.get_sql().toString());
=09=09return null;
=09=09// return sql;
=09}

=09ISQLExecutionListener() { }
=09ISQLExecutionListener(SIMarksPlugin homebase)
=09{
=09=09log.info("SQL Listener established");
=09=09home =3D homebase;
=09=09home.store_sql("xxxxx");
=09=09log.info(home.get_sql().toString());
=09}


}

%%%%% end of excerpt 1 %%%%%%%%%%%%%


%%%% start excerpt 2 %%%%%%%%

     public PluginSessionCallback sessionStarted(final ISession session) {
     =09final ISQLPanelAPI sqlapi =3D =20
session.getSQLPanelAPIOfActiveSessionWindow();

     =09final ISQLExecutionListener foo =3D new ISQLExecutionListener(this);
     =09s_log.info("created listener of class " + =20
((ISQLExecutionListener)foo).getClass().toString());

     =09sqlapi.addSQLExecutionListener((ISQLExecutionListener)foo);

     =09s_log.info("At init, sql history is: " + =20
sqlapi.getSQLHistoryItems().get(0));
     =09return new SIMarksPluginSessionCallback(this);
     }

%%%% end of excerpt 2 %%%%%%%%%%%%

Hello,

currently when we do a CSV export, the default charset is used.
This is sometimes a problem, since you can't specify which encoding you=20
will have.

For this to change, we only need to change the second line of writeCSV=20
in TableExportCsvCommand.java to:

BufferedWriter bw =3D new BufferedWriter(new=20
java.io.OutputStreamWriter(fw, fileEncoding));

The file encoding can then be specified as a parameter.
Unfortunately I have not enough swing experience to add a encoding popup=20
to the export dialog. (File TableExportCsvDlg.java)

Anyone who could tell me how to do it ?

Andr=E9

Hi Thorsten,

I updated the translations page to regard your work on the German translation. I 
hope that's alright with you.

Thanks for your work on the data import plugin. I tried it out and find it very 
useful :-). I attached a first little patch for it to remember the directory of 
the last used import file. I just attached the complete file instead of a patch. 
I hope you don't. Of course if you want me to I can commit the patch.


Gerd

Thorsten Mürell wrote:
> Hello,
> 
> today, I committed a new version of the dataimport plugin. It is a complete 
> rewrite of the old one, which I found very unusable.
> 
> Perhaps someone can check it out, test the functionality and send me all bugs, 
> errors and comments to help me to improve the plugin. The help pages will 
> show you how to use it.
> 
> I also included it in the list of plugins for the weekly snapshot so that it 
> is will also soon be available for users. I know of some, that are awaiting 
> it.
> 
> Greetings,
> 
> Thorsten
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> 

Hi, there was a discussion on this list earlier about whether to add
LiquiBase support to the existing refactoring plug-in, or create a
different one.  In case you didn't read through it all, the end result
was that since LiquiBase doesn't support as many databases, it would be
better to start it as a separate plug-in.

Here's my current status on the LiquiBase plugin:
I started with adding some sample table-level refactorings.  They have
dialogs that allow you to specify needed parameters, execute the change
against your database, and save the change to a hard-coded change log
file.

I was in the process of figuring out the best way to handle preferences
for the location of the changelog files and changelog classpaths as well
as a good UI for handling column level refactorings when I decided to
focus more of the LiquiBase core migrator and take a break from the
plug-in.

If you are interested in continuing where I left off, I'd be happy to
send you the source code and more in depth thoughts on features it
should have.

Nathan

-----Original Message-----
From: squ...@li...
[mailto:squ...@li...] On Behalf Of
Stefan Keller
Sent: Wednesday, June 13, 2007 2:55 PM
To: squ...@li...
Subject: Re: [Squirrel-sql-develop] Refactoring Plugin


Nathan, Rob, all

I am interested in refactoring databases and would like to know the
status
and plans to enhance the original refactoring plugin (and possibly the
other
one)?

Currently it seems to support mainly add, modify and drop for table,
columns
and pk. This corresponds to the structural refactorings - but there are
more
as it's nicely compiled here
http://www.liquibase.org/supported_refactorings.html=20

-- Stefan
--=20
View this message in context:
http://www.nabble.com/Refactoring-Plugin-tf3696577.html#a11107622
Sent from the squirrel-sql-develop mailing list archive at Nabble.com.


------------------------------------------------------------------------
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Nathan, Rob, all

I am interested in refactoring databases and would like to know the status
and plans to enhance the original refactoring plugin (and possibly the other
one)?

Currently it seems to support mainly add, modify and drop for table, columns
and pk. This corresponds to the structural refactorings - but there are more
as it's nicely compiled here
http://www.liquibase.org/supported_refactorings.html 

-- Stefan
-- 
View this message in context: http://www.nabble.com/Refactoring-Plugin-tf3696577.html#a11107622
Sent from the squirrel-sql-develop mailing list archive at Nabble.com.

On 6/11/07, Thorsten M=FCrell <tho...@gm...> wrote:
> Hello,
>
> today, I committed a new version of the dataimport plugin. It is a comple=
te
> rewrite of the old one, which I found very unusable.
>
> Perhaps someone can check it out, test the functionality and send me all =
bugs,
> errors and comments to help me to improve the plugin. The help pages will
> show you how to use it.
>
> I also included it in the list of plugins for the weekly snapshot so that=
 it
> is will also soon be available for users. I know of some, that are awaiti=
ng
> it.
Very nice work! This functionality was sorely missed at times. Thanks
for volunteering to make the plugin usable.  I'll give it a try and
let you know if I find any issues.

Rob

Hello,

today, I committed a new version of the dataimport plugin. It is a complete 
rewrite of the old one, which I found very unusable.

Perhaps someone can check it out, test the functionality and send me all bugs, 
errors and comments to help me to improve the plugin. The help pages will 
show you how to use it.

I also included it in the list of plugins for the weekly snapshot so that it 
is will also soon be available for users. I know of some, that are awaiting 
it.

Greetings,

Thorsten

I've refactored the code to allow plugins to register an
ExceptionFormatter with a session, which will allow plugin writers to
provide customization of messages derived from vendor-specific
SQLExceptions.  Specifically, I introduced facade methods in ISession
that mimick the interface of IMessageHandler and pass the
ExceptionFormatter into the IMessageHandler interface methods that
accept a Throwable.  At first it seemed logical to register the
ExceptionFormatter with the IMessageHandler.  However, there is only
one instance of IMessageHandler (MessagePanel) that all sessions have
a reference to, so that proved unworkable.  It seemed logical to allow
Sessions to have a default exception formatter that a plugin can
override.  So that is what I went with.  Of course, when working
outside the context of a Session, the IMessageHandler interface can be
given null for the ExceptionFormatter and it will use it's own default
ExceptionFormatter.  When more than one plugin attempts to override
the ExceptionFormatter for a given Session, the first one to do so
wins and any thereafter result in an error message.  The most
noticeable change will be for showing messages in the MessagePanel.
No longer will you do this:

} catch (SQLException ex) {
    _session.getMessageHandler().showErrorMessage(ex)
}

But instead you will do this:

} catch (SQLException ex) {
    _session.showErrorMessage(ex)
}

Same arguments as before, just not going directly to the
IMessageHandler.  Again, this was necessary to allow the Session to
pass it's custom ExceptionFormatter (if any) to the new
IMessageHandler interface methods that accept Throwable and
ExceptionFormatter.
As before, this can be bypassed by going directly to Application and
getting the IMessageHandler - however, this should be done sparingly
as it prevents plugins from formatting exceptions and potentially
providing users with more information about the root cause of the
problem causing the exception.

Rob Manning

That may be best.  I was hoping the session properties were specific to =
each session, I was going to test that out after I got them saving, but =
now I don't have to, thanks.  I figured I do them as global properties =
as a fallback if need be.
=20
Nathan

________________________________

From: Robert Manning [mailto:rob...@gm...]
Sent: Mon 6/4/2007 5:15 PM
To: Nathan Voxland
Cc: squ...@li...
Subject: Re: [Squirrel-sql-develop] Somehow broke session properties =
dialog



On 6/4/07, Nathan Voxland <Nat...@su...> wrote:
> Mainly I need a way to configure the file(s) that the refactorings are
> saved to.  I thought the session configuration would be the best place
> to store it, because a person may want different configurations based =
on
> the session.

The trouble with that is Session properties aren't session-specific.
In other words, when you change session settings, then *all* future
sessions get that change, if you save them via "New Session
Properties".  Maybe a global preference that allows them to set an
output directory and then pick the filename in the plugin based on the
session saving the refactoring?

Rob

On 6/4/07, Nathan Voxland <Nat...@su...> wrote:
> Mainly I need a way to configure the file(s) that the refactorings are
> saved to.  I thought the session configuration would be the best place
> to store it, because a person may want different configurations based on
> the session.

The trouble with that is Session properties aren't session-specific.
In other words, when you change session settings, then *all* future
sessions get that change, if you save them via "New Session
Properties".  Maybe a global preference that allows them to set an
output directory and then pick the filename in the plugin based on the
session saving the refactoring?

Rob

I'll take a look.  Thanks.

Nathan

-----Original Message-----
From: Robert Manning [mailto:rob...@gm...]=20
Sent: Monday, June 04, 2007 3:10 PM
To: Nathan Voxland
Cc: squ...@li...
Subject: Re: [Squirrel-sql-develop] popup menus for columns

On 6/4/07, Nathan Voxland <Nat...@su...> wrote:
> Is there anywhere that lists columns besides in the table?  The only
> thing that shows up in the tree under each table is "triggers".  Is
this
> a limitation of Oracle, or do columns not show up for any database?
>
> What I'm wanting to do is add a menu for column refactorings (change
> type, add not null constraint, etc.)  Where can I do that from a
plugin?

SQuirreL doesn't represent columns as tree objects.  The only way to
see a column is to click on the columns tab when a table is selected
(certain other objects have columns to).  You have a couple of
options:

1. In the plugin you could implement a column expander for tables
(some plugins add trigger expanders to create a "Triggers" folder
beneath tables where individual triggers can be selected in the object
tree).    See TriggerParentExpander and TriggerParentInfo for an
example of this.  Also there are IndexParentExpander / IndexParentInfo
classes likewise for index nodes under tables.

2. You could do as I did with the current refactoring plugin and just
add a menu-item to the popup for tables in the object tree.  I did it
this way because it was easy to do and it didn't occur to me to add
column expanders at the time.  Wish I had thought of that...

Rob

Mainly I need a way to configure the file(s) that the refactorings are
saved to.  I thought the session configuration would be the best place
to store it, because a person may want different configurations based on
the session.

Nathan

-----Original Message-----
From: Robert Manning [mailto:rob...@gm...]=20
Sent: Monday, June 04, 2007 3:21 PM
To: Nathan Voxland
Cc: squ...@li...
Subject: Re: [Squirrel-sql-develop] Somehow broke session properties
dialog

On 6/4/07, Nathan Voxland <Nat...@su...> wrote:
> No exceptions in the log.  Just INFO messages about other plugins
being
> created.

Just curious - what would be session-specific about the refactoring
plugin? (Note: session properties that are persisted between sessions
are global to all new sessions. Session settings that are not
persisted, go away when the session is closed)

Rob

On 6/4/07, Nathan Voxland <Nat...@su...> wrote:
> No exceptions in the log.  Just INFO messages about other plugins being
> created.

Just curious - what would be session-specific about the refactoring
plugin? (Note: session properties that are persisted between sessions
are global to all new sessions. Session settings that are not
persisted, go away when the session is closed)

Rob

On 6/4/07, Nathan Voxland <Nat...@su...> wrote:
> Is there anywhere that lists columns besides in the table?  The only
> thing that shows up in the tree under each table is "triggers".  Is this
> a limitation of Oracle, or do columns not show up for any database?
>
> What I'm wanting to do is add a menu for column refactorings (change
> type, add not null constraint, etc.)  Where can I do that from a plugin?

SQuirreL doesn't represent columns as tree objects.  The only way to
see a column is to click on the columns tab when a table is selected
(certain other objects have columns to).  You have a couple of
options:

1. In the plugin you could implement a column expander for tables
(some plugins add trigger expanders to create a "Triggers" folder
beneath tables where individual triggers can be selected in the object
tree).    See TriggerParentExpander and TriggerParentInfo for an
example of this.  Also there are IndexParentExpander / IndexParentInfo
classes likewise for index nodes under tables.

2. You could do as I did with the current refactoring plugin and just
add a menu-item to the popup for tables in the object tree.  I did it
this way because it was easy to do and it didn't occur to me to add
column expanders at the time.  Wish I had thought of that...

Rob

Is there anywhere that lists columns besides in the table?  The only
thing that shows up in the tree under each table is "triggers".  Is this
a limitation of Oracle, or do columns not show up for any database?

What I'm wanting to do is add a menu for column refactorings (change
type, add not null constraint, etc.)  Where can I do that from a plugin?

-----Original Message-----
From: Robert Manning [mailto:rob...@gm...]=20
Sent: Monday, June 04, 2007 2:12 PM
To: Nathan Voxland
Cc: squ...@li...
Subject: Re: [Squirrel-sql-develop] popup menus for columns

On 6/4/07, Nathan Voxland <Nat...@su...> wrote:
>
>
>
>
> I've been able to add menus to the table popup menus fine, but I am
having
> troubles adding them for columns.
>
Nathan,

The code for table popups lives in the fw (framework) module (see
DataSetViewerEditableTablePanel for instance).  The plugin api you are
attempting to use deals with the object tree and columns aren't
presented there.  I don't believe there is a way to specify customized
table popup entries from plugins.

Rob

No exceptions in the log.  Just INFO messages about other plugins being
created.



-----Original Message-----
From: Robert Manning [mailto:rob...@gm...]=20
Sent: Monday, June 04, 2007 2:13 PM
To: Nathan Voxland
Cc: squ...@li...
Subject: Re: [Squirrel-sql-develop] Somehow broke session properties
dialog

On 6/4/07, Nathan Voxland <Nat...@su...> wrote:
> I was working on creating a session properties dialog for a plugin and
> suddenly the session properties dialog is no longer displaying.  I've
tried
> deleting my .squirrel-sql directory, and running squirrel without my
new
> plugin, but the dialog still does not display.  It does show up under
the
> "Windows" dialog, but it's not visible.

Any exceptions in the log?

Rob

On 6/4/07, Nathan Voxland <Nat...@su...> wrote:
> I was working on creating a session properties dialog for a plugin and
> suddenly the session properties dialog is no longer displaying.  I've tried
> deleting my .squirrel-sql directory, and running squirrel without my new
> plugin, but the dialog still does not display.  It does show up under the
> "Windows" dialog, but it's not visible.

Any exceptions in the log?

Rob

On 6/4/07, Nathan Voxland <Nat...@su...> wrote:
>
>
>
>
> I've been able to add menus to the table popup menus fine, but I am having
> troubles adding them for columns.
>
Nathan,

The code for table popups lives in the fw (framework) module (see
DataSetViewerEditableTablePanel for instance).  The plugin api you are
attempting to use deals with the object tree and columns aren't
presented there.  I don't believe there is a way to specify customized
table popup entries from plugins.

Rob

On 6/4/07, Bobby Kent <Bob...@in...> wrote:
> I work for Emma McGrattan, SVP Engineering at Ingres, and she's asked me to
> develop an Ingres plugin for SQuirreL SQL.  The document at
> http://squirrel-sql.sourceforge.net/paper/SQuirreL_us.pdf
> advises that getting in touch with this list first is a good idea, so here I
> am.  I've read through the description of building the example DB2 plugin
> and it seems fairly straightforward, though it's good to know there's
> somebody I can contact should issues arise.

Bobby,

It's nice to see someone step forward to implement this plugin.  There
are many things that can be done to enhance SQuirreL's behavior when
working with a particular database.  Most of the work - besides
learning the plugin API - is writing the SQL for reading the database
system catalog.  You can look at the existing plugins to get some
ideas.  The Oracle plugin probably provides the greatest level of
customization, but others are worth looking at as well.  If you have
any questions at all feel free to post them to this list.

Rob