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

Hi,

> I have been using SQuirreL for the last few months and gave a shot at 
> advocacy by trying to convince techSupport/helpDesk to use SQuirreL for 
> users who needed a SQl tool as opposed to some $$$$ alternatives.

Exactly what I like to hear :-)

> While the first might seem odd it really isnt. When they did install the
1.4 
> jre on some machines it ended up by default setting itself up as the
plugin 
> for IE. This broke some old internal apps that used the default jre
supplied 
> with IE and Netscape. They ended up solving the issues but it caused a 
> headache.
> Is there any way that SQuirreL can be shipped with a JRE that doesn't 
> install? Meaning a JRE that would just be in the SQuirreL bin dir and just

> be used for SQuirreL? This would obviously be a much larger DL (obviously 
> SQurreL should be avail without a bundled JRE as well) but would make it 
> much simpler to install.

This isn't something I want to do as it complicates the release process and
I don't have enough time to work on SQuirreL as it is. Nor do I believe that
applications should be installing multiple versions of VMs on PCs, you can
end up in quite a mess.

When the JRE is installed you can specify which browsers you want the java
plugin to be used by. All your tech support has to do is to change it not to
specify IE or Netscape. Or after the install they can use the control panel
to change the default VM back to what it is originally. Here at my work
these kinds of settings are locked down so that if I change them they get
changed back to what they should be automatically.

> The second one I can't argue with because I dont know what setup they are 
> using for other tools. To me setting it up seemed easy (was a while ago so
I 
> dont fully remember the details) but it seemingly has to be simplified.
Its 
> possible that it was setting up drivers etc that isnt necessary for other 
> non java based tools.
> Is there a way this can be simplified?

Without knowing what it is they found complicated I cannot really answer the
question however this may help.

Theres two pieces of config requried to connect to a database.

1. Point the driver definition to the driver jars.

2. Create an alias.

For the driver definition if the JDBC drivers are installed in the
%CLASSPATH% (Windows) or $CLASSPATH (Unix/Linux) or if they have been copied
to the jre/lib/ext directory then no configuration of the SQuirreL driver
definition is necessary. SQuirreL will just use the drivers. In fact any
Java application on the PC will be able to use the drivers.

Theres no getting around point 2, however it can be simplified. Install
SQuirreL on a PC and create the aliases that you want everybody to have
access to. I assume that the installer for SQuirreL would be on a network
share so copy up the file <users home>/.squirrel-sql/SQLAliases.xml to the
network share. Then install SQuirreL on a second PC. Copy the file
SQLAliases.xml from the network share to the same place on the second PC. A
simple batch file or shell script could take care of this.

Col

-----Original Message-----
From: L Rutker [mailto:lr...@ho...]
Sent: Sunday, 22 June 2003 14:50
To: squ...@li...
Subject: [Squirrel-sql-develop] Tech Support Gave Up On SquirreL


Hi,
I have been using SQuirreL for the last few months and gave a shot at 
advocacy by trying to convince techSupport/helpDesk to use SQuirreL for 
users who needed a SQl tool as opposed to some $$$$ alternatives.
They gave it a try but gave up.
Here were the reasons:
a) needs an up to date jvm
b) config issues.

While the first might seem odd it really isnt. When they did install the 1.4

jre on some machines it ended up by default setting itself up as the plugin 
for IE. This broke some old internal apps that used the default jre supplied

with IE and Netscape. They ended up solving the issues but it caused a 
headache.
Is there any way that SQuirreL can be shipped with a JRE that doesn't 
install? Meaning a JRE that would just be in the SQuirreL bin dir and just 
be used for SQuirreL? This would obviously be a much larger DL (obviously 
SQurreL should be avail without a bundled JRE as well) but would make it 
much simpler to install.
The second one I can't argue with because I dont know what setup they are 
using for other tools. To me setting it up seemed easy (was a while ago so I

dont fully remember the details) but it seemingly has to be simplified. Its 
possible that it was setting up drivers etc that isnt necessary for other 
non java based tools.
Is there a way this can be simplified?

Lou

_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*  
http://join.msn.com/?page=features/virus



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

L Rutker wrote:
> Hi,
> Colin's mail last week about not using jdk 1.4 due to osx issues has me=
=20
> wondering.
> What will the impact of the lack of 1.4 support be to everyone else ?=20
> are there features that will be missing due to the non use of 1.4 or is=
=20
> it just that use of some new "easier to code with" 1.4 methods will not=
=20
> be used?
>=20
> Lou

It's the second guess, "things" already available or easier done in=20
1.4 will be there, but implemented more complicated.

--=20
Freundliche Gr=FC=DFe/Kind Regards       Victor Ott
Salutari cordiale/Saludos cordiales  victor.ott at q-dsl dot de

Hi,
I have been using SQuirreL for the last few months and gave a shot at 
advocacy by trying to convince techSupport/helpDesk to use SQuirreL for 
users who needed a SQl tool as opposed to some $$$$ alternatives.
They gave it a try but gave up.
Here were the reasons:
a) needs an up to date jvm
b) config issues.

While the first might seem odd it really isnt. When they did install the 1.4 
jre on some machines it ended up by default setting itself up as the plugin 
for IE. This broke some old internal apps that used the default jre supplied 
with IE and Netscape. They ended up solving the issues but it caused a 
headache.
Is there any way that SQuirreL can be shipped with a JRE that doesn't 
install? Meaning a JRE that would just be in the SQuirreL bin dir and just 
be used for SQuirreL? This would obviously be a much larger DL (obviously 
SQurreL should be avail without a bundled JRE as well) but would make it 
much simpler to install.
The second one I can't argue with because I dont know what setup they are 
using for other tools. To me setting it up seemed easy (was a while ago so I 
dont fully remember the details) but it seemingly has to be simplified. Its 
possible that it was setting up drivers etc that isnt necessary for other 
non java based tools.
Is there a way this can be simplified?

Lou

_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*  
http://join.msn.com/?page=features/virus

Hi,
Colin's mail last week about not using jdk 1.4 due to osx issues has me 
wondering.
What will the impact of the lack of 1.4 support be to everyone else ? are 
there features that will be missing due to the non use of 1.4 or is it just 
that use of some new "easier to code with" 1.4 methods will not be used?

Lou

_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

Just a quick note to let everybody know. SQuirreL 1.2 will require JDK
1.3.1, not JDK 1.4.x because of problems with JDK 1.4 on OS X.

Col

Kymerix http://kymerix.com/ is an organization created to promote open 
source Java desktop applications. Each month they will be doing a 
feature on a Java application. This month they have done one on 
SQuirreL which you can read at http://kymerix.com/reviews/squirrel.html

--
Colin Bell
http://squirrel-sql.sf.net

Hi Ruffin,

Sorry I've been flat out at work and am only now catching up with my emails.

> In Microsoft SQL Server's Query Manager, I can select one or many database
> objects, hit ctrl-c, and have the schema for the table(s) (text, natch) in
> my clipboard.  AWFULLY handy.  Worth pursuing in SQuirreL?

The SQL scripts plugin does something similar, it generates CREATE TABLE
statements and places them in the SQL entry area. By schema do you mean
CREATE TABLE statements or something else?

On the other stuff it seems that you'll need some changes in the SQuirreL
core:

- New Session  - setting continue/abort on error. When executing multiple
SQL statments, if one fails should the next ones be executed?

- A way for plugins to interrogate and/or modify the _complete_ SQL script
prior to it being split and executed.

I can do those once I've got the first beta of 1.2 out.

Col

PS I'm away for the next few days so I'll be appearing to ignore emails
again :-)


-----Original Message-----
From: Ruffin Bailey [mailto:Ruf...@Bl...]
Sent: Wednesday, 4 June 2003 1:02
To: squ...@li...
Cc: col...@te...
Subject: [Squirrel-sql-develop] Get table schema & RE: Auto DROP
[object]...


A "feature request/can I do this", and a fwd of a message that hasn't come
through just yet (sent May 20th; sorry if it "deluges" later).

In Microsoft SQL Server's Query Manager, I can select one or many database
objects, hit ctrl-c, and have the schema for the table(s) (text, natch) in
my clipboard.  AWFULLY handy.  Worth pursuing in SQuirreL?

Second bit is my reply for the Auto DROP function -- basically just looking
to use on VIEWs, so should be relatively safe.  Adding a pref for tables too
is a good idea.  Email quoted below.

Thanks!

Ruffin Bailey

Ruffin Bailey wrote on Tuesday, May 20, 2003 10:58 AM:

>  [Another possibility would be to look at the SQL prior to it being
executed
>  and if there is a CREATE TABLE command then execute a DROP command
first.]
> 
> The problem of course is that this would throw an error if
> the table/view/whatever object *didn't* exist before the
> statement the user created executed.  Squ'l could silently
> bitbucket the error thrown by the unnecessary drop statement,
> I suppose, and though it's somewhat kludgey that's a valid route, I think.
> 
> [There is an API
> ISQLPanelAPI.addSQLExecutionListener(ISQLExecutionListener)
>  that allows you to look at SQL before it is executed and if necessary
>  modify it.
> ...
>  In your case you'd probably want to look at the SQL _before_ its split
into
>  the three statements and then add a DROP TABLE to the start.]
> 
> That sounds like a good way of doing it, again if you could bitbucket any
> errors there. 
> 
> [Because I'm a very nervous person I would want this behaviour to be
>  configurable. I.E. have an application setting something like 'Auto drop
>  tables before create true/false" with the default being false so that the
>  user has to change it to true if they want this behaviour.]
> 
> That's a good idea -- I normally wish I had this feature when
> I'm making reports and optimizing views and sprocs, in which
> case an accidental drop isn't such a big deal.  Guess the
> best way to go is to set up different settings for each
> object type.  Might set up the plugin to drop views by
> default, but you'd have to manually change settings for other types.  ??
> 
> I like the way you started using single quotes for your
> quote, above.  Wonder where that came from?  ;^)
> 
> Thanks for your help,
> 
> Ruffin Bailey


-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

A "feature request/can I do this", and a fwd of a message that hasn't =
come through just yet (sent May 20th; sorry if it "deluges" later).

In Microsoft SQL Server's Query Manager, I can select one or many =
database objects, hit ctrl-c, and have the schema for the table(s) =
(text, natch) in my clipboard.  AWFULLY handy.  Worth pursuing in =
SQuirreL?

Second bit is my reply for the Auto DROP function -- basically just =
looking to use on VIEWs, so should be relatively safe.  Adding a pref =
for tables too is a good idea.  Email quoted below.

Thanks!

Ruffin Bailey

Ruffin Bailey wrote on Tuesday, May 20, 2003 10:58 AM:

>  [Another possibility would be to look at the SQL prior to it being =
executed
>  and if there is a CREATE TABLE command then execute a DROP command =
first.]
>=20
> The problem of course is that this would throw an error if
> the table/view/whatever object *didn't* exist before the
> statement the user created executed.  Squ'l could silently
> bitbucket the error thrown by the unnecessary drop statement,
> I suppose, and though it's somewhat kludgey that's a valid route, I =
think.
>=20
> [There is an API
> ISQLPanelAPI.addSQLExecutionListener(ISQLExecutionListener)
>  that allows you to look at SQL before it is executed and if necessary
>  modify it.
> ...
>  In your case you'd probably want to look at the SQL _before_ its =
split into
>  the three statements and then add a DROP TABLE to the start.]
>=20
> That sounds like a good way of doing it, again if you could bitbucket =
any
> errors there.=20
>=20
> [Because I'm a very nervous person I would want this behaviour to be
>  configurable. I.E. have an application setting something like 'Auto =
drop
>  tables before create true/false" with the default being false so that =
the
>  user has to change it to true if they want this behaviour.]
>=20
> That's a good idea -- I normally wish I had this feature when
> I'm making reports and optimizing views and sprocs, in which
> case an accidental drop isn't such a big deal.  Guess the
> best way to go is to set up different settings for each
> object type.  Might set up the plugin to drop views by
> default, but you'd have to manually change settings for other types.  =
??
>=20
> I like the way you started using single quotes for your
> quote, above.  Wonder where that came from?  ;^)
>=20
> Thanks for your help,
>=20
> Ruffin Bailey

> The problem of course is that this would throw an error if the
> table/view/whatever object *didn't* exist before the statement
> the user created executed.  Squ'l could silently bitbucket the
> error thrown by the unnecessary drop statement, I suppose, and
> though it's somewhat kludgey that's a valid route, I think.

This brings up a point I hadn't thought of. SQSC probably needs a new
session setting "Continue on error true/false". E.G. in this example if any
of the SQL statements failed you wouldn't want to continue with the others:

create table tab01 
(
	key int,
	data varchar
};
insert into tab01 values(1, 'abc');
select * from tab01;

But if you were running multiple inserts and some were going to fail because
a row with the primary key already existed then you might want to continue
on with the other inserts. E.G.

insert into tab01 values(1, 'abc');
insert into tab01 values(2, 'def'); /* 2 is already in the table */
insert into tab01 values(3, 'ghi');

Col

Hi Stathis,

Thanks, that works very nicely. I've taken the liberty of sending this to
the developers list as I believe its more appropriate there.

If you want we can release the plugin without any real help file, it just
means that anybody who wants to use it will have to dig into the source code
and most people won't do that.

For everybody on the list who doesn't know what iSqlJ is its a way of mixing
Java and SQL. From the web site http://www.rege.org/isqlj/ :

"The iSqlJ is an interpreter which combines the strength points of both SQL
and Java. It uses the BeanShell for Java interpretation and JDBC for SQL
execution. Then, you can write programs which mix Java code and SQL
statements.

If you are writing SQL programs which consists from a lot of SQL statements,
then propably the iSqlJ is written for you. If additionally you want to
parameterize those programs, then definitely iSqlJ will fit your need. If
finally you want to add functionality of Java to your SQL statements, then
you are going to love it. "

From SQuirreLs point of view its a plugin that makes SQuirreL scriptable,
and it looks very, very powerful.

The problem is that theres very little documentation. Stathis has been too
busy getting it to work to write the documentation. Also English is not his
first language which makes documentation very difficult. And I think that
Stathis (like most of us) doesn't like doing documentation (from the web
site - " Help others to use the program by writing documentation for it. I
hate any other writing than coding, and that explains why this site is so
lazy. Please help me to improve it and make people to understand the
features of iSqlJ more easy.")

If somebody on this list has an interest in iSqlJ and would like to help out
please reply to this message, Stathis is subscribed to this list.

Stathis, I hope you don't mind me sending this message. I doing it out of
pure selfishness :-)  I'd really like to see iSqlJ documented sufficiently
that I could sit down and start using it seriously.

Col

-----Original Message-----
From: Stathis.Rege [mailto:st...@re...]
Sent: Tuesday, 20 May 2003 21:24
To: Colin Bell; 'Denis Grannell'
Cc: squ...@li...
Subject: RE: [Squirrel-sql-users] Bug when displaying user defined data
types?


Hi Collin and Denis

I possibly have an immediate solution for this problem.

1. Try to install the sqsc-isqlj plugin located in www.rege.org/isqlj/.
2. Start a session. and write  the following statement


jdbc.getDatabase().dropTable( "foo_%");
#sql[session]
{
    create table foo_1
    (
        .......
    );
    create table foo_2
    (
        .......
    );
}


3. Select all of the code and press Control J. Propably you will have the
feature you wanted.


This will happen because i allready implemented a small parser able to run
mixed Java and SQL. I made also a plugin for SquirrelSql client.
Inside this parser exists a Database class which has the dropTable method.


I know that i did not documented, i have no excuse. I will do my best when i
will have some time.


Best regards


Stathis Alexopoulos


-----Original Message-----
From: Ruffin Bailey [mailto:Ruf...@Bl...]
Sent: Wednesday, 21 May 2003 0:58
To: squ...@li...
Subject: [Squirrel-sql-develop] RE: Auto DROP [object] on CREATE [object
a already existing in db]


 [Another possibility would be to look at the SQL prior to it being executed
 and if there is a CREATE TABLE command then execute a DROP command first.]

The problem of course is that this would throw an error if the
table/view/whatever object *didn't* exist before the statement the user
created executed.  Squ'l could silently bitbucket the error thrown by the
unnecessary drop statement, I suppose, and though it's somewhat kludgey
that's a valid route, I think.

[There is an API ISQLPanelAPI.addSQLExecutionListener(ISQLExecutionListener)
 that allows you to look at SQL before it is executed and if necessary
modify
 it.
...
 In your case you'd probably want to look at the SQL _before_ its split into
 the three statements and then add a DROP TABLE to the start.]

That sounds like a good way of doing it, again if you could bitbucket any
errors there.

[Because I'm a very nervous person I would want this behaviour to be
 configurable. I.E. have an application setting something like 'Auto drop
 tables before create true/false" with the default being false so that the
 user has to change it to true if they want this behaviour.]

That's a good idea -- I normally wish I had this feature when I'm making
reports and optimizing views and sprocs, in which case an accidental drop
isn't such a big deal.  Guess the best way to go is to set up different
settings for each object type.  Might set up the plugin to drop views by
default, but you'd have to manually change settings for other types.  ??

I like the way you started using single quotes for your quote, above.
Wonder where that came from?  ;^)

Thanks for your help,

Ruffin Bailey

 [Another possibility would be to look at the SQL prior to it being =
executed
 and if there is a CREATE TABLE command then execute a DROP command =
first.]

The problem of course is that this would throw an error if the =
table/view/whatever object *didn't* exist before the statement the user =
created executed.  Squ'l could silently bitbucket the error thrown by =
the unnecessary drop statement, I suppose, and though it's somewhat =
kludgey that's a valid route, I think.

[There is an API =
ISQLPanelAPI.addSQLExecutionListener(ISQLExecutionListener)
 that allows you to look at SQL before it is executed and if necessary =
modify
 it.
...
 In your case you'd probably want to look at the SQL _before_ its split =
into
 the three statements and then add a DROP TABLE to the start.]

That sounds like a good way of doing it, again if you could bitbucket =
any errors there.

[Because I'm a very nervous person I would want this behaviour to be
 configurable. I.E. have an application setting something like 'Auto =
drop
 tables before create true/false" with the default being false so that =
the
 user has to change it to true if they want this behaviour.]

That's a good idea -- I normally wish I had this feature when I'm making =
reports and optimizing views and sprocs, in which case an accidental =
drop isn't such a big deal.  Guess the best way to go is to set up =
different settings for each object type.  Might set up the plugin to =
drop views by default, but you'd have to manually change settings for =
other types.  ??

I like the way you started using single quotes for your quote, above.  =
Wonder where that came from?  ;^)

Thanks for your help,

Ruffin Bailey

Hi Ruffin,

> I haven't checked another plugin to see how difficult it'd be to add,
> but a catch of the error that an object already exists on a CREATE
> with an automatic DROP of the correct object if it does would be awful
> helpful to me.

I'm not sure how easy this would be. The problem would be identifying
whether the create failed because the table is already there or for some
other reason such as the syntax of the CREATE TABLE command being incorrect,
in a way that will work with all DBMS's.

Another possibility would be to look at the SQL prior to it being executed
and if there is a CREATE TABLE command then execute a DROP command first.
There is an API ISQLPanelAPI.addSQLExecutionListener(ISQLExecutionListener)
that allows you to look at SQL before it is executed and if necessary modify
it. For the following SQL ISQLExecutionListener.statementExecuting(String)
will be called three times, once for each statement.

create table tab01 
(
	key int,
	data varchar
};
insert into tab01 values(1, 'abc');
select * from tab01;

In your case you'd probably want to look at the SQL _before_ its split into
the three statements and then add a DROP TABLE to the start. I could add
another method to ISQLExecutionListener to allow you to do this. Let me know
what you think.

Because I'm a very nervous person I would want this behaviour to be
configurable. I.E. have an application setting something like 'Auto drop
tables before create true/false" with the default being false so that the
user has to change it to true if they want this behaviour. My big worry
would be dropping an existing table because the table name in the CREATE
TABLE was misspelt or because the user didn't realize that a table with that
name already existed.

Col

-----Original Message-----
From: Ruffin Bailey [mailto:Ruf...@Bl...]
Sent: Tuesday, 20 May 2003 2:05
To: squ...@li...
Subject: [Squirrel-sql-develop] Auto DROP [object] on CREATE [object
already existing in db]


>If you have got an idea for a plugin just send a message to the SQuirreL
>Developers list giving a brief description.  This helps to ensure that two
>people don't develop the same plugin.

Okay, I will.  ;^)

I've wasted a lot of time over the years slapping, "DROP VIEW foo; CREATE
VIEW foo..." in isql tools, and of course have wasted more time adding the
"--" in "--DROP VIEW foo;" to the statements when the CREATE didn't work the
first time, I modify it, and accidentally try to give both statements
another shot.

I haven't checked another plugin to see how difficult it'd be to add, but a
catch of the error that an object already exists on a CREATE with an
automatic DROP of the correct object if it does would be awful helpful to
me.

Anybody started?  Any pointers?

Thanks,

Ruffin Bailey


-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful, 
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
_______________________________________________
Squirrel-sql-develop mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

>If you have got an idea for a plugin just send a message to the =
SQuirreL
>Developers list giving a brief description.  This helps to ensure that =
two
>people don't develop the same plugin.

Okay, I will.  ;^)

I've wasted a lot of time over the years slapping, "DROP VIEW foo; =
CREATE VIEW foo..." in isql tools, and of course have wasted more time =
adding the "--" in "--DROP VIEW foo;" to the statements when the CREATE =
didn't work the first time, I modify it, and accidentally try to give =
both statements another shot.

I haven't checked another plugin to see how difficult it'd be to add, =
but a catch of the error that an object already exists on a CREATE with =
an automatic DROP of the correct object if it does would be awful =
helpful to me.

Anybody started?  Any pointers?

Thanks,

Ruffin Bailey

Can you send is as a CVS patch?
Else send it as a source code
then i will check youre changes in.

johan

----- Original Message ----- 
From: "Stathis Alexopoulos" <st...@co...>
To: <jco...@j-...>
Cc: <squ...@li...>
Sent: Sunday, May 11, 2003 10:40 AM
Subject: [Squirrel-sql-develop] Shortcut keys for sqlscripts plugin of Squirrel-sql


> Hi Johan
> 
> My name is Stathis Alexopoulos, and i found your plugin very usefull to me.
> Unfortunatelly, when i am developing thinks i am pressing the save key more
> frequently than
> enter key, so i was needed an easier save procedure for your plugin.
> 
> I downloaded your code and i made the following changes.
> 1. SaveScriptAction renamed to SaveAsScriptAction.
> 2. SaveScriptAction replicated and changed the behavior of actionperformed
> to avooid the display of SaveDialog when
> SAVE_SCRIPT_FILE_PATH_KEY is not null.
> 3. In properties file added accelator key for SaveScripAction.
> 4. The rest of source was slightly modified to allow the new feature. (added
> to menu, in initialization procedure..)
> 
> I am satisfied from the changes and now i am using them in my installation
> and some guys in my company appreciated it also.
> I think that it would be interested also for many users of your plugin.
> If you want to add these changes, either i can send you my source code or i
> can apply them to CVS.
> By the way i left the copyright untouched, and the new class has the same
> copyright info with previous classes naming
> you as author.
> 
> 
> I hope that i am not bother you in any way, and i will be happy if you apply
> the new feature to your plugin.
> 
> 
> 
> Thanks in advance
> 
> 
> Stathis Alexopoulos
> 
> 
> 
> 
> 
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Hi Johan

My name is Stathis Alexopoulos, and i found your plugin very usefull to me.
Unfortunatelly, when i am developing thinks i am pressing the save key more
frequently than
enter key, so i was needed an easier save procedure for your plugin.

I downloaded your code and i made the following changes.
1. SaveScriptAction renamed to SaveAsScriptAction.
2. SaveScriptAction replicated and changed the behavior of actionperformed
to avooid the display of SaveDialog when
SAVE_SCRIPT_FILE_PATH_KEY is not null.
3. In properties file added accelator key for SaveScripAction.
4. The rest of source was slightly modified to allow the new feature. (added
to menu, in initialization procedure..)

I am satisfied from the changes and now i am using them in my installation
and some guys in my company appreciated it also.
I think that it would be interested also for many users of your plugin.
If you want to add these changes, either i can send you my source code or i
can apply them to CVS.
By the way i left the copyright untouched, and the new class has the same
copyright info with previous classes naming
you as author.


I hope that i am not bother you in any way, and i will be happy if you apply
the new feature to your plugin.



Thanks in advance


Stathis Alexopoulos

Hi Stathis,

Welcome back, hope you had a good holiday.

I've just put your plugin up in in CVS - /sql12/plugins/isqlj

Theres an API to allow plugins to store arbitrary info in the session, Its
within ISession

Object getPluginObject(IPlugin plugin, String key);
Object putPluginObject(IPlugin plugin, String key, Object obj);
void removePluginObject(IPlugin plugin, String key);

Col

----- Original Message -----
From: "Stathis.Rege" <st...@re...>
To: <squ...@li...>
Sent: Wednesday, May 07, 2003 7:33 PM
Subject: [Squirrel-sql-develop] Session properties


> Hi Colin,
>
> Finally, I am back. I have modified my code according your suggestions,
but
> i am waiting
> to put the sqsc-isqlj on cvs before apply them. Please give me your
> instructions if there is a need
> to do something about it.
>
> Except that, i woulg like to change the sql-scripts plugin which is very
> usefull to me and i excessively use it.
> In fact, what i would like from this plugin was to have a <Control S>
> shortcut to continuously saving my scripts
> in the time that i am writing.
> In order to do that, there is a need to memorize the filename of script
> which is in use from that session and i think
> i can with a minor change to plugin. But i was wondering if there is a
> general mechanism on squirrel-sql having session
> properties. Could you point me where to look if it exists?
>
>
> Best regards
>
>
> Stathis Alexopoulos
>
>
>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop

Hi Colin,

Finally, I am back. I have modified my code according your suggestions, but
i am waiting
to put the sqsc-isqlj on cvs before apply them. Please give me your
instructions if there is a need
to do something about it.

Except that, i woulg like to change the sql-scripts plugin which is very
usefull to me and i excessively use it.
In fact, what i would like from this plugin was to have a <Control S>
shortcut to continuously saving my scripts
in the time that i am writing.
In order to do that, there is a need to memorize the filename of script
which is in use from that session and i think
i can with a minor change to plugin. But i was wondering if there is a
general mechanism on squirrel-sql having session
properties. Could you point me where to look if it exists?


Best regards


Stathis Alexopoulos

Version 0.31 of the Look and Feel Plugin has
been released. Downloads can be found here:

https://sourceforge.net/project/showfiles.php?group_id=28383&release_id=156824

This plugin allows you to change the Look
and Feel for SQuirreL SQL Client, as well as
change the font used. It ships with several
Look and Feel implementations.

Requires at least JDK1.3 and SQuirreL SQL
Client 1.1final1. To install you need to
download the appropriate .zip or .tar.gz file
and unpack it into the plugins directory
within the SQuirreL SQL Client
application making sure that you keep the
directory structure.

Bug Fixes
---------
- the default Metal Theme (Steel) can now be Specified.


--
Colin Bell
http://squirrel-sql.sf.net
 

Version 0.30 of the Look and Feel Plugin has
been released. Downloads can be found here:

http://sourceforge.net/project/showfiles.php?group_id=28383&release_id=156391

This plugin allows you to change the Look
and Feel for SQuirreL SQL Client, as well as
change the font used. It ships with several
Look and Feel implementations.

Requires at least JDK1.3 and SQuirreL SQL
Client 1.1final1. To install you need to
download the appropriate .zip or .tar.gz file
and unpack it into the plugins directory
within the SQuirreL SQL Client
application making sure that you keep the
directory structure.

Enhancements
---------------------
- Improved plugin startup time.
- Skin Look and Feel updated to 1.2.3.
- Now supports themes for the Metal Look
  and Feel.
- Plastic Look and Feel added.

Bug Fixes
---------
- If a themepack/skin hasn't been specified
  then default to the first one in the
  dropdown in the preferences dialog.
- Only change the current Look and Feel
  when a new Look and Feel is actually
  selected in the preferences dialog.

Other
-----
- Display the licences for all the supplied Look
  and Feel implementations in the Licence
  menu option.

--
Colin Bell
http://squirrel-sql.sf.net

 

This is the first release of a new, "SQL 
Bookmark" plugin for SQuirrel-SQL. This 
plugin allows you to manage commonly used 
SQL code for easy reuse. The plugin also 
provides a simple syntax for parameter 
replacement within the bookmarked SQL. As 
the SQL is reloaded, the user is prompted to 
enter values for any embedded parameters, 
after which the SQL is loaded into the edit 
buffer for execution. 

The plugin requires SQuirreL SQL Client 
1.1final1 and JDK 1.3+. 

To install you need to download the 
appropriate .zip or .tar.gz file and unpack it 
into the plugins directory within the SQuirreL 
SQL Client application making sure that you 
keep the directory structure. 

Downloads can be found at: 
http://sourceforge.net/project/showfiles.php?
group_id=28383&release_id=155627

--
Colin Bell
http://squirrel-sql.sf.net
 

Hi Joe,

SQLBookmark sounds interesting. Both the bookmark facility and the
parameterized queries are features that have been requested for SQSC. Do
you have a download link to your plugin so that I can have a look at it?

--
Colin Bell
http://squirrel-sql.sf.net

----- Original Message -----
From: Joe Mocker <mo...@mi...>
Date: Monday, April 14, 2003 2:21 am
Subject: [Squirrel-sql-develop] new squirrel sql plugin

> Hello,
> 
> I've been working on a plugin for Squirrel SQL that I would like
> to share. I've been calling SQLBookmark. As the name would 
> imply, it allows you to "bookmark" frequently use SQL statements
> and easily reload them into the SQL buffer.
> 
> Additionally, it provides a syntax for specifying parameters
> to be replaced at load time. 
> 
> Could someone send me a pointer to info on how to proceed on
> getting this plugin listed with the others on sourceforge ?
> 
> Thanks...
> 
>  --joe

 

Hello,

I've been working on a plugin for Squirrel SQL that I would like
to share. I've been calling SQLBookmark. As the name would 
imply, it allows you to "bookmark" frequently use SQL statements
and easily reload them into the SQL buffer.

Additionally, it provides a syntax for specifying parameters
to be replaced at load time. 

Could someone send me a pointer to info on how to proceed on
getting this plugin listed with the others on sourceforge ?

Thanks...

  --joe

Hello all,

First of all, i have to express my many thanks for your excellent job. The
SquirrelSQL client
is by far my favorite SQL client editor. I replaced all other tools i used
with your client.
I dont know if i can help so much as you helped me, but i will not miss any
opportunity to do so.

Last week i made something which could be usefull also for you. I created a
small interpreter which
parses something like SQLJ programs.
This interpreter reads a sequence of characters and separating the tokens in
two distinct language blocks.
The Java statements and SQL statements. The Java statements are passed to
BeasnSell for execution. The SQL
statemens are passed to JDBC also for execution.

I wrote this program, because i wanted to have parametirized SQL programs.
The result was not
only the parametirization, but the ability of writing a mix of Java and SQL
statements. I will give you
an example.

samplesNo = new Integer( args[0});
sampleDate = args[1];
for( int i = 0; i < samplesNo; i++)
{
    sample = Math.random();
    toolType = Math.round( Math.random() * 5.0);
    #sql[session] { insert into samples (sn, tool, ammount) values({:i},
{:toolType}, {:sample}) }
}
#sql[session]
{
    update tool set noise = (select avg( ammount) from samples where
tool.type = samples.tool;
    update tool set maxLevel = maxLevel - noise where noise > 0.0005;
}

Currently, user executes those scripts with a command in the following form.
ISQLJ CREATE_SAMPLES.SQL 100 "2003/04/10"

My next goal is to use the SquirrelSQL client to execute those scripts. I
started to look at plugins,
but in the plugins.html i found the method statementExecuting(String sql).
If i unerstood correct, the
SquirrelSQL parsing the selected text and giving back one by one the scanned
SQL statements.
In my case the selected text block will contain a mix of Java and SQL code.

Is it possible to hooked up before the scanning? Is it completely wrong my
way?

If you are interesting and want to help me, i will appreciated.



Thanks in advance


Stathis Alexopoulos

> Is there anything specifically new in 1.4.1 from 1.3.1 that you 
> are 
> hoping to incorporate directly, that can't be done how it is 
> currently 
> (i.e. checking for existence of 1.4.1 specific classes and only 
> then 
> loading appropriate classes via reflection)?

There are a couple of reasons I want to move to 1.4. Firstly there have
been a number of issues with 1.3, mainly Swing problems that go away
with 1.4. Having to test everything with 1.3 as well as 1.4 has been a
real pain, not to mention developing workarounds for bugs in 1.3.

Secondly there are new features in 1.4 that will be useful. regex, JSSE,
 new drag and drop architecture etc. Yes these can be accessed via
reflection but it means that any functionality that relies on them will
not be available when running on 1.3.

Eventually I will drop support for JDK 1.3. At the latest it will be
when Sun bring out their first release of java 1.5. However I would like
to do it before then.

> The JDK 1.4.1 update for Mac OS X is optional, and I'm actually 
> working 
> with a development group who is specifically avoiding the upgrade. 
> They 
> may not be alone in this regard.

All upgrades are optional but there comes a time when you have to apply
them or nothing will run. I can understand taking your time with the
upgrade, as regression testing etc would be required but avoiding it
puzzles me. Are there known problems with the upgrade that would make
people avoid it?

--
Colin Bell
http://squirrel-sql.sf.net

----- Original Message -----
From: Lynn Pye <ly...@py...>
Date: Wednesday, April 2, 2003 12:10 pm
Subject: [Squirrel-sql-develop] Re: SQuirreL 1.1 and JDK 1.4

> The JDK 1.4.1 update for Mac OS X is optional, and I'm actually 
> working 
> with a development group who is specifically avoiding the upgrade. 
> They 
> may not be alone in this regard.
> 
> Is there anything specifically new in 1.4.1 from 1.3.1 that you 
> are 
> hoping to incorporate directly, that can't be done how it is 
> currently 
> (i.e. checking for existence of 1.4.1 specific classes and only 
> then 
> loading appropriate classes via reflection)?
> 
> Lynn
> 
> On Tuesday, April 1, 2003, at 03:38  PM, 
> squ...@li... wrote:
> 
> >
> > Message: 1
> > From: Colin Bell <col...@te...>
> > To: squ...@li...,
> > 	 squ...@li...
> > Reply-To: col...@bi...
> > Date: Tue, 01 Apr 2003 17:06:24 +1000
> > Subject: [Squirrel-sql-develop] SQuirreL 1.1 and JDK 1.4
> >
> > Now that Apple has finally released Java 1.4 for OS X, all the 
> > platforms
> > that SQuirreL runs on have Java 1.4. I'd like to make 1.4.0 the 
> minimum> version of Java required for the next release of SQuirreL.
> >
> > Are there any objections to this?
> >
> > --
> > Colin Bell
> > http://squirrel-sql.sf.net
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: ValueWeb: 
> Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
> No other company gives more support or power for your dedicated server
> http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> 
 

The JDK 1.4.1 update for Mac OS X is optional, and I'm actually working 
with a development group who is specifically avoiding the upgrade. They 
may not be alone in this regard.

Is there anything specifically new in 1.4.1 from 1.3.1 that you are 
hoping to incorporate directly, that can't be done how it is currently 
(i.e. checking for existence of 1.4.1 specific classes and only then 
loading appropriate classes via reflection)?

Lynn

On Tuesday, April 1, 2003, at 03:38  PM, 
squ...@li... wrote:

>
> Message: 1
> From: Colin Bell <col...@te...>
> To: squ...@li...,
> 	 squ...@li...
> Reply-To: col...@bi...
> Date: Tue, 01 Apr 2003 17:06:24 +1000
> Subject: [Squirrel-sql-develop] SQuirreL 1.1 and JDK 1.4
>
> Now that Apple has finally released Java 1.4 for OS X, all the 
> platforms
> that SQuirreL runs on have Java 1.4. I'd like to make 1.4.0 the minimum
> version of Java required for the next release of SQuirreL.
>
> Are there any objections to this?
>
> --
> Colin Bell
> http://squirrel-sql.sf.net