ijsql-devel — development list for iJSQL

[Ijsql-devel] Fw: Happy Holidays

[William G. <ww...@ts...>]

Hello, folks --

Peter never received this email, so I'm resending it ...

I haven't had time to do any more work since sending this originally, so the
code is still as it's described in the email below.

Regards,
Bill Graham

----- Original Message -----
From: "William Graham" <ww...@ts...>
To: <Ijs...@li...>
Sent: Tuesday, December 26, 2000 12:44 AM
Subject: Happy Holidays


> Dear Jukka, Peter, and Glen --
>
> Happy Holidays !!!
>
> Hope the season finds all of you well and happy.
>
> iJSQL update:
>
> I have the architecture divided: currently there's  the core class,
> iJSQL.java, and a console view class, iJSQL_Console.java.  Jukka's
> switchable connections are working, and I have tested it with InstantDB
and
> MS Access (using the jdbcodbc bridge). I'm javadoccing the code now, and
> will try to sort out cvs to get it checked in.  I've gone ahead and
attached
> the code as a zip archive, if you want to take a look.  As I said, it's
not
> commented much yet ...
>
> I've implemented the packaging I proposed, working Jukka's plugins into
the
> core tree:
> com.curiousmuse.ijsql.core
>     com.curiousmuse.ijsql.core.plugin
>     com.curiousmuse.ijsql.core.pluginsamples
> com.curiousmuse.ijsql.view
>     com.curiousmuse.ijsql.view.console
>     com.curiousmuse.ijsql.view.gui
>
> I also added a LOAD option to the core iJSQL class: if the statement is in
> the format "LOAD <driver classname>", the specified driver is loaded.
Also,
> if you specify "LOAD <driver classname> <connection string> [<username>]
> [<password>]", the driver is loaded, then a connection is established to
the
> specified db/user/password.  This connection then becomes the current
> connection.
>
> Right now, no drivers are loaded when you start an app.  You must use the
> LOAD command from the commandline.  Here's my idea on how to handle this:
we
> supply a sample properties file with some common drivers specified.  The
> user can edit these to get the initial setup configured (for the gui view,
> maybe there's a nice Swing interface to do this).  The app attempts to
load
> these on startup.  Any drivers that are LOADed by the user are added to
the
> properties file, or replace the current entries.
>
> Any input on what I've done is welcome.  One area I'd like feedback on is
> the treatment of the member variables in the core iJSQLclass.  It's not a
> "pure" OO approach ... what do you think??
>
> Best Regards,
> Bill Graham
>

Re: [Ijsql-devel] Happy Holidays

[William G. <ww...@ts...>]

> Right now, no drivers are loaded when you start an app.

This isn't totally true ... sorry.  You do have th option of specifying a
driver on the commandline when you start up.

java com.curiousmuse.ijsql.view.console.iJSQL_Console <driver classname>
<conn string> [user] [password]

Also, you'll probably figure this out, but the make.bat and runconsole.bat
will probably need to be modified for your environments ...

Regards,
Bill Graham

[Ijsql-devel] Happy Holidays

[William G. <ww...@ts...>]

Dear Jukka, Peter, and Glen --

Happy Holidays !!!

Hope the season finds all of you well and happy.

iJSQL update:

I have the architecture divided: currently there's  the core class,
iJSQL.java, and a console view class, iJSQL_Console.java.  Jukka's
switchable connections are working, and I have tested it with InstantDB and
MS Access (using the jdbcodbc bridge). I'm javadoccing the code now, and
will try to sort out cvs to get it checked in.  I've gone ahead and attached
the code as a zip archive, if you want to take a look.  As I said, it's not
commented much yet ...

I've implemented the packaging I proposed, working Jukka's plugins into the
core tree:
com.curiousmuse.ijsql.core
    com.curiousmuse.ijsql.core.plugin
    com.curiousmuse.ijsql.core.pluginsamples
com.curiousmuse.ijsql.view
    com.curiousmuse.ijsql.view.console
    com.curiousmuse.ijsql.view.gui

I also added a LOAD option to the core iJSQL class: if the statement is in
the format "LOAD <driver classname>", the specified driver is loaded.  Also,
if you specify "LOAD <driver classname> <connection string> [<username>]
[<password>]", the driver is loaded, then a connection is established to the
specified db/user/password.  This connection then becomes the current
connection.

Right now, no drivers are loaded when you start an app.  You must use the
LOAD command from the commandline.  Here's my idea on how to handle this: we
supply a sample properties file with some common drivers specified.  The
user can edit these to get the initial setup configured (for the gui view,
maybe there's a nice Swing interface to do this).  The app attempts to load
these on startup.  Any drivers that are LOADed by the user are added to the
properties file, or replace the current entries.

Any input on what I've done is welcome.  One area I'd like feedback on is
the treatment of the member variables in the core iJSQLclass.  It's not a
"pure" OO approach ... what do you think??

Best Regards,
Bill Graham

[Ijsql-devel] Code separation

[William G. <ww...@ts...>]

Hello, all --

Well, I'm finally getting a bit of time to devote to iJSQL ...

I've published the starting coding guidelines to the site under
documentation.  I don't think it's visible yet, but should be there soon.
Again, these standards are open to discussion.

Also, I'm deep in the process of separating out the core and view code,
making the core into an api that's useable by any choice of presentation
layer.  My goal is just to get us to a good starting point, where other
views and other features are easy to add.  There will undoubtedly be changes
needed to what I do.

I'll get this working and into cvs as soon as I can.  Jukka, it also has
your switchable connections, from the code you sent me a while back.  If
anyone else is currently working on any coding that will need to be
included, let me know so I can integrate it.  You'll get full credit in the
changelog and my cvs checkin comment.  If you'd rather have the checkin to
cvs show your name, wait until I check in, then integrate your changes and
check them in yourself.

CVS needs cleaning up.  I'll dig into the Sourceforge site docs to try to
figure out how to get things fixed, and under the com.curiousmuse.ijsql
package structure.

Regards,
Bill Graham

[Ijsql-devel] first cut at coding standards

[William G. <ww...@ts...>]

This is probably not complete, but let's get started deciding on this.

Note:
1) almost all of this is open for discussion.  If you disagree with any of
this, have additions, or have better ways of doing things, let's discuss it
on the list.
2) the initial code that I wrote doesn't necessarily follow all of these
rules, since I was writing it as a "one-off" app that I didn't think would
ever be used by anyone else.  Bad assumption on my part   ;-)      Part of
re-architecting the code will be to modify it to conform to the final coding
standards we agree on.

----------------------------------------

Naming
* Class Names - proper case
 example: " public class TestDbConnection "
* Method Names - lower case first portion, then uppercase the beginnings of
subsequent words
 example: " public String getDatabaseName "
* Variable Names - same format as method names, except for member variables,
covered next.
* Member Variable Names - prefixed with "m_"
 example: " private String m_dbName "

Braces & Indentation
* Braces on the line following the declaration, and indented to the same
spot
* Indent each new nesting level 4 spaces
* Convert tabs to spaces (I think most editors can be set to do this)

Exception handling
* Prefer to throw exceptions up to the top level, i.e., the presentation
layer.  Core code should basically be an api, and should not handle
exceptions itself.  There may be cases where the core code does need to
handle exceptions, and this should be decided on a case-by-case basis.

OO and Coding Philosophy
* Define interfaces for our classes.  Bind on these interfaces, rather than
on the concrete classes

* Challenge the existence of non-static member vars: are they only used in
one method? If so, they should probably be loval variables declared in that
method.

* There should be accessor (get / set) methods for any member vars that
require visibility outside the class itself.

* Try to keep method size down: if a method starts getting large and
convoluted, see if there are parts that stand alone, and can be extracted to
other methods.

* Prefer composition to inheritance: use the basic tests to determine which
to use: "is a" vs. "has a", etc.

* Javadoc your code, at the method and class level.  Use appropriate
comments throughout the code, without belaboring the obvious, i.e., you
don't need to do something like this:

    //load the value of the first column in the ResultSet into a temp string
    String tmp = rs.getString(1);

However, if there's some compelling reason that might not be obvious why
you're performing the operation, comment that.

Re: [Ijsql-devel] Re: tasks and the like

[William G. <ww...@ts...>]

Hi, Glen --

> FYI:  Together software (www.togethersoft.com) offers a free product for
> creating Java class diagrams.

Together is a very nice tool.  However, the free version doesn't do as much
as the expensive versions: does it allow you to export to html (I can't
remember ...)?

I like Together, but I think that for the design doc, other tools are more
suitable.  It's a great tool for use by developers, though: if the rest of
you haven't looked at it, follow Glen's link and try out the free version.
It reverse engineers your code into class diagrams, also, which is cool to
get a handle on someone else's code, etc.

Regards,
Bill G,

[Ijsql-devel] Re: tasks and the like

[Glen K. <gl...@ho...>]

>Also, I would assume that saving the result into an HTML file would be ok 
>not knowing all parties access to tools.

FYI:  Together software (www.togethersoft.com) offers a free product for 
creating Java class diagrams.
_____________________________________________________________________________________
Get more from the Web.  FREE MSN Explorer download : http://explorer.msn.com

Re: [Ijsql-devel] Re: Tasks and the like

[William G. <ww...@ts...>]

Hi, Peter --

> Just so I understand the scope of this document - do you want a "Visio"
type
> diagram which shows all major areas, or a system flow ... "class diagrm" -
> like with high level objects ...

I think a fairly simple class diagram would be fine for right now.  As you
say, the next step would be a "meatier" diagram.  We can expand it then.

> Also, I would assume that saving the result into an HTML file would be ok

HTML is perfect.  That way, everyone can look at it regardlesss of platform.

> do you have any ideas on the naming convention you would like for the
packages ?

Yeah, we've sort of run out of time on the package naming convention.  I
still have heard nothing from Sourceforge, so I'm going to make the decision
that we use my domain name, which is curiousmuse.com.  If Sourceforge ever
answers that yes, we can use the Sourceforge name in the package, we can
think about switching.  For now, how about something like:

[core code]
com.curiousmuse.ijsql.core;

    [jdbc/metadata code]
    com.curiousmuse.ijsql.core.db;

    [cross-db]
    com.curiousmuse.ijsql.core.xdb;

    [xml-related]
    com.curiousmuse.ijsql.core.xmltools;

    [any common utils]
    com.curiousmuse.ijsql.core.utils;

[presentation/view]
com.curiousmuse.ijsql.view;

    [console view]
    com.curiousmuse.ijsql.view.console;

    [gui view]
    com.curiousmuse.ijsql.view.gui;

    [servlet view]
    com.curiousmuse.ijsql.view.web;

This is off the top of my head; any comments, different opinions, or
objections are welcome.  Also, the above probably doesn't cover everything
...

Anyone out there a CVS wizard?  We need to restructure cvs to match the
package structure.  If noone else is already an expert, I'll dig into the
docs and do it.

Regards,
Bill Graham

[Ijsql-devel] Re: Tasks and the like

[Peter K. <pk...@ho...>]

Bill,

Just so I understand the scope of this document - do you want a "Visio" type 
diagram which shows all major areas, or a system flow ... "class diagrm" - 
like with high level objects ...

Also, I would assume that saving the result into an HTML file would be ok 
not knowing all parties access to tools.  Also, since the next step should 
be a diagram with some meat, do you have any ideas on the naming convention 
you would like for the packages ?

Regards,

Peter



>From: "William Graham" <ww...@ts...>
>To: "Peter Kasson" <pk...@ho...>
>CC: <Ijs...@li...>
>Subject: Re: Tasks and the like
>Date: Fri, 1 Dec 2000 00:09:05 -0800
>
>Hello, Peter --
>
> > Yes, the cross-db stuff, xml, metadata and the like are probably a lot 
>for
> > the first release.
>
>Well, the expansion of the metadata querying (task 3) should be easy; I've
>already been thinking on that, and will add it in shortly.  Jukka already
>has the code for switchable multiple db connections.  What other "major"
>function or functions do you think we should target for initial release?
>
> > I would like to see code generation as well, and possibly options like
>pool
> > managers ... etc., but certainly for v.2
>
>Once we define what's in this release, let's rough out a release list for
>the next couple of versions.
>
> > I tried out the gui code in the CVS project, but only got the connect
>panel.
> >   The code looks like it has a JTree and the like, but could not get it 
>up
> > and running ... have you ?
>
>Not recently: I know that it does require a class from the borland jar file
>that's also in cvs.  Did you get that & put it in the classpath?  I can try
>to get it running myself soon, too.  Also, I can get the "author", my 
>friend
>Stefan, to give us a hand   ;-)
>
> > Task distribution - how would this be done ?
>
>Not totally sure.  I'd like to see if anyone has any areas they prefer to
>work on.  One area I want to keep working on is the basic console version,
>since that's what I originally wrote, and what I use day-to-day at my work.
>I'm hoping that others will just make their preferences / interests known,
>and we can go from there.
>
> > I have 5+ databases at my office to work with, on Linux and NT (Oracle,
> > SQL-Server, MySQL, Interbase (Inprise), JDataStore, MSAccess as well as
> > other xBase type databases.  I can do some development on these as well 
>as
> > testing.
>
>Cool.  I have Oracle and Mysql on Linux, and InstantDB on Linux and 
>Windows.
>Sounds like we have a good range if things -- you just about have it all!
>Anyone else have any other dbms or platforms available for test?
>
> > Should there be anything as elaborate as class diagrams, modeling and 
>the
> > like being done here?  I have all the tools necessary and would offer my
> > services as documenter if others want to do upfront design or want to
>lead.
> > I can do the design of these things as well, but wonder if this is
>overkill
> > (at least a few high-level diagrams would be good I think).
>
>A class diagram, basic design, and perhaps a message flow diagram, will be
>very nice as we separate into a MVC architecture (assuming that's the
>approach we use to separate view from core code: other architecture
>suggestions, anyone?), and as we add the sort of things you and Jukka are
>talking about.  I don't want us to go too "design-crazy", but don't want to
>make the opposite mistake either.  Let's see if anyone else has any 
>comments
>about design, then we'll add some basic design tasks into the release 
>tasks.
>
>One thing I do want to do is get us to agree on some coding conventions.
>I'd also like to go back and comment the code, and then require javadoc at
>the beginning of each class and method.  This will make maintenance and
>expansion much easier in the future ...
>
>Thanks again for the input!  Anyone else have comments / ideas /
>objections??
>
>Regards,
>Bill Graham
>

_____________________________________________________________________________________
Get more from the Web.  FREE MSN Explorer download : http://explorer.msn.com

Re: [Ijsql-devel] tasks for premier release, and roll call

[Glen K. <gl...@ho...>]

I'm still interested.  Also I'm pretty flexible as to what tasks I'll take.  
I have no problem doing Swing stuff if no one else wants it.

Glen K
sa...@us...
_____________________________________________________________________________________
Get more from the Web.  FREE MSN Explorer download : http://explorer.msn.com

[Ijsql-devel] tasks for premier release, and roll call

[William G. <ww...@ts...>]

Hello --

I've added subprojects and tasks to iJSQL for the premier release.  The
latest completion date I have specified is January 7, 2001, for now.  I
have not included everything we've talked about.  If there are any features
that you think should be included in the premier that I've left out, let me
know.

I'll probably  advertise for a QA person soon.  I might also advertise for a
Swing GUI person, unless someone on the team wants to work in that area.
Peter, you mentioned that you were willing to do it, but you didn't sound
enthusiastic.  If you want it, that's fine; otherwise, I'll advertise and
see what we come up with.

Also, please respond to this email if you wish to keep participating in the
project.  I'm just wanting to see who is listening and still wanting to
participate.  I'm assuming that Jukka, Peter, and Glen are still in: correct
me if I'm wrong.  Denymon, are you here?  You're very welcome to
participate, if you still want to.

No hard feelings if anyone wants out!    :)

Best Regards,
Bill Graham

Re: [Ijsql-devel] tasks for premier release

[William G. <ww...@ts...>]

I'll be trying to get the tasks into the Sourceforge system today or
tonight.  Once they're in, we'll need to assign tasks.  Once again, if
anyone hasn't already told me what they would like to work on, please let me
know!

Regards,
Bill Graham

Re: [Ijsql-devel] tasks for premier release

[Jukka U. <juk...@vt...>]

Sorry, 

I haven't been around for some days but now i am back :)

This task list is great job, and some thoughts came up

Wed, 29 Nov 2000, Bill Wrote :
> My thoughts on tasks;  these need to be prioritized and pared down, as not
> all of these should be "immediates".  Please comment, add, object, give
> thoughts on priorities, etc.  My priority list is at the bottom.
> 
> MAIN ARCHITECTURAL STEP:
> 1) separate "engine" and presentation layers, perhaps using
> Model-View-Controller architecture; the goal is to have presentation totally
> decoupled from the core code, so that "pluggable" presentations are easy.
>

I think this is number one. Should be first thing before even plan
anything else. 

 
 
> CORE CODE TASKS:

> 
> 4) switchable connections to multiple db`s.  This was Jukka`s idea, and is
> in code he sent me: Jukka, is it in cvs yet?
> 

Not yet,  but asap i hope. :)

> 5) get rid of the hard-coded Class.forName(drivername) stuff at the
> begining; I`m leaning toward putting the driver classnames into a properties
> file so they can be read in and loaded.  The version of code that was
> checked in to cvs has this, but it`s not been tested at all (compiles ...
> ;-)
> 

Maybe this can be done by using command "load/unload <driver>" . Few days
 i tested different versions of  Solid drivers and this kind of feature might
be nice. But maybe drivers named in properties file is ok in version 1.

>
> 6) look at exception handling: right now, the tool crashes if there`s a
> SQLException.  it should just print a warning and continue on, especially if
> it`s because of something like a typo in a query ...
> 

I think this is basic functinality and must work. Normally exceptions are not
fatal errors.

>
> 7) Jukka and Peter: multi-db queries, two phase commits for premier release,
> or is this further in the future?
> 

IHMO, this is not necessery for premier release but we should keep that in mind
so we can "leave door open for this one".

>
> 8) decide on a package name; I still haven't heard from Sourceforge on using
> "net.sourceforge.ijsql".
> 

I think this is also one of fist things. If net.sourceforge is not avalable,
maybe we just use Bill's domain name if that is avalable? 

We need real package name, but we should not make this too hard thing.

> 
> VIEW-ORIENTED TASKS:
> 
> 14) Servlet and/or JSP view: do we want a defined, standard servlet or jsp
> view, or do we just want the core code as pluggable as possible?  Or both?
> ;-)

I think this goes hand in hand with first architectural step and our aim should 
be to make core code as pluggable as possible. If we make good separation
with core code and user interface code, there should not be big thing to do 
gui/console/servlet or whatever user interface or just api-level interface to
iJsql.

[Ijsql-devel] Re: Tasks and the like

[Peter K. <pk...@ho...>]

Hi Bill,

>Jukka already has the code for switchable multiple db connections.

When you say "switchable", what does that infer ?  I was thinking of the 
x-db query in more depth and need to peruse the JDBC 2.0 specs.  I am hoping 
it supports such a beast, else, it may be a bit of a conundrum.

Certainly, the data extraction and transformation is what I'm interested in 
possibly more than x-db.  I have done this in things like SQL-Server DTS and 
manually, but am envisioning a GUI like DTS which would allow for this to 
happen -- it has real awesome possibilities.

>Not recently: I know that it does require a class from the borland jar file
>that's also in cvs.  Did you get that & put it in the classpath?  I can try
>to get it running myself soon, too.  Also, I can get the "author", my 
>friend
>Stefan, to give us a hand   ;-)

I did build the app ok and run it - but haven't donated a lot of time to it. 
  Were you looking to leverage this front end?  If so, it needs a bit of 
clean up and polishing (and as I say, if one suggests something, they should 
be willing to do it) so I could take that on if no one else wants to.

>
>Not totally sure.  I'd like to see if anyone has any areas they prefer to
>work on.  One area I want to keep working on is the basic console version,
>since that's what I originally wrote, and what I use day-to-day at my work.
>I'm hoping that others will just make their preferences / interests known,
>and we can go from there.
>


As I mentioned already, I would like to pursue the "DTS" portion and 
possibly the front-end cleanup.  Part of this front-end would encapsulate 
the "console" mode if desired - but using a "GUI" console.  This would give 
the console more functionality and you could switch between GUI and console. 
  Have you seen Oracle 8i's "SQL-Plus" worksheet?  Kind of like that.


>A class diagram, basic design, and perhaps a message flow diagram, will be
>very nice as we separate into a MVC architecture (assuming that's the
>approach we use to separate view from core code: other architecture
>suggestions, anyone?)


MVC is the basis for much of the Swing stuff, so it fits nicely.


>One thing I do want to do is get us to agree on some coding conventions.
>I'd also like to go back and comment the code, and then require javadoc at
>the beginning of each class and method.  This will make maintenance and
>expansion much easier in the future ...
>


Definitely.  I don't want to get into a religious debate when we suggest 
certain standards or coding conventions.  Javadoc is a must and it would be 
nice if at the class level, have an example of usage.


This is all good.  Tell you what, I will do a couple of high-level docs and 
email them to you and Jukka and let's discuss.  Sooner we get consensus, we 
can get cooking !


Regards,

Peter Kasson


_____________________________________________________________________________________
Get more from the Web.  FREE MSN Explorer download : http://explorer.msn.com

Re: [Ijsql-devel] re: tasks

[<ww...@ts...>]

Quoting Glen Koundry <gl...@ho...>:

> I have Sybase 11.5 running under WindowsNT and SQL
Server 7 running under
> Windows 2000 at work.

Great!  that gives us some more testbed platforms.

Regards,
Bill Graham

=========================================
This mail sent through Sinclair's WebMail
      http://mail.sinclair.net

[Ijsql-devel] Re: Tasks and the like

[<ww...@ts...>]

Quoting Peter Kasson <pk...@ho...>:
> When you say "switchable", what does that infer ?

It means that you can have connections open to multiple
databases, and can switch between them; in a console,
for example, I might be connected to an Oracle db, then
hit a hotkey combination to get a new connection and
connect to my Sybase db; once they're both open, I can
switch back and forth between them.

> I was thinking of the x-db query in more depth and
> need to peruse the JDBC 2.0 specs.  I am
> hoping it supports such a beast, else, it may be a bit
of a conundrum.

Could we implement it manually, also, by defining a
cross-db join syntax, then preprocessing the query?  The
preprocessor would have to be able to determine how to
retrieve the info from each database, then merge the
results ... yes, a bit of a beast, perhaps.  Fun,
though!   ;-)

> Certainly, the data extraction and transformation is
what I'm interested in 
> possibly more than x-db.  I have done this in things
like SQL-Server DTS
> and manually, but am envisioning a GUI like DTS which
would allow for this to
> happen -- it has real awesome possibilities.

Sounds like a great area for you to be working on  
;-)   and I agree that it would be awsome.

> I did build the [Swing gui] app ok and run it - but
haven't donated a lot of time to
> it.  Were you looking to leverage this front end?  If
so, it needs a bit of
> clean up and polishing (and as I say, if one suggests
something, they 
> should be willing to do it) so I could take that on if
no one else wants to.

I would like to leverage the front end; yes, it needs
clean up (Stefan was a bit sheepish about donating the
code, since he knew it needed the cleanup, too   ;-)

You're welcome to work on it, but it sounds like you're
more interested in the DTS-like functionality;  let's
see if someone else who just LOVES Swing work wants to
help ... If noone on the project currently wants to do
it, I'll place another job add specifically for Swing
GUI help.

>Part of this front-end would encapsulate
> the "console" mode if desired - but using a "GUI"
console.  This would give
> the console more functionality and you could switch
between GUI and
> console. Have you seen Oracle 8i's "SQL-Plus"
worksheet? Kind of like that.

I have seen it, but I also want to keep a pure
character-based console view available, like SQL*Plus. 
That way, there's a nice, advanced cross-db query tool
available to me to open in an Emacs shell when I'm doing
development, or for when I'm working outside of
X-Windows.  The pure gui/gui console version you
describe would be great!  and I hope we get that, but I
do want to keep the text-mode console as well.  This
should be very easy, once we do the MVC.

> Definitely.  I don't want to get into a religious
debate when we suggest
> certain standards or coding conventions.  Javadoc is a
must and it would be
> nice if at the class level, have an example of usage.

Right.  I don't want religious wars, but would like some
standards so that the code has some consistency.  I have
a few ideas I'll post separately a bit later, then we
can hash things out and agree on some standards.

> This is all good.  Tell you what, I will do a couple
of high-level docs and
> email them to you and Jukka and let's discuss.  Sooner
we get consensus, we
> can get cooking !

Great! Thanks once again for all the ideas and input!

Regards,
Bill Graham



=========================================
This mail sent through Sinclair's WebMail
      http://mail.sinclair.net

[Ijsql-devel] Fwd: Re: Tasks and the like

[<ww...@ts...>]

----- Forwarded message from Peter Kasson
<pk...@ho...> -----
Date: Fri, 01 Dec 2000 09:14:46 -0500
From: Peter Kasson <pk...@ho...>
Reply-To: Peter Kasson <pk...@ho...>
Subject: Re: Tasks and the like
To: ww...@ts...

Hi Bill,

>Jukka already has the code for switchable multiple db
connections.

When you say "switchable", what does that infer ?  I was
thinking of the
x-db query in more depth and need to peruse the JDBC 2.0
specs.  I am hoping
it supports such a beast, else, it may be a bit of a
conundrum.

Certainly, the data extraction and transformation is
what I'm interested in
possibly more than x-db.  I have done this in things
like SQL-Server DTS and
manually, but am envisioning a GUI like DTS which would
allow for this to
happen -- it has real awesome possibilities.

>Not recently: I know that it does require a class from
the borland jar file
>that's also in cvs.  Did you get that & put it in the
classpath?  I can try
>to get it running myself soon, too.  Also, I can get
the "author", my
>friend
>Stefan, to give us a hand   ;-)

I did build the app ok and run it - but haven't donated
a lot of time to it.
  Were you looking to leverage this front end?  If so,
it needs a bit of
clean up and polishing (and as I say, if one suggests
something, they should
be willing to do it) so I could take that on if no one
else wants to.

>
>Not totally sure.  I'd like to see if anyone has any
areas they prefer to
>work on.  One area I want to keep working on is the
basic console version,
>since that's what I originally wrote, and what I use
day-to-day at my work.
>I'm hoping that others will just make their preferences
/ interests known,
>and we can go from there.
>


As I mentioned already, I would like to pursue the "DTS"
portion and
possibly the front-end cleanup.  Part of this front-end
would encapsulate
the "console" mode if desired - but using a "GUI"
console.  This would give
the console more functionality and you could switch
between GUI and console.
  Have you seen Oracle 8i's "SQL-Plus" worksheet?  Kind
of like that.


>A class diagram, basic design, and perhaps a message
flow diagram, will be
>very nice as we separate into a MVC architecture
(assuming that's the
>approach we use to separate view from core code: other
architecture
>suggestions, anyone?)


MVC is the basis for much of the Swing stuff, so it fits
nicely.


>One thing I do want to do is get us to agree on some
coding conventions.
>I'd also like to go back and comment the code, and then
require javadoc at
>the beginning of each class and method.  This will make
maintenance and
>expansion much easier in the future ...
>


Definitely.  I don't want to get into a religious debate
when we suggest
certain standards or coding conventions.  Javadoc is a
must and it would be
nice if at the class level, have an example of usage.


This is all good.  Tell you what, I will do a couple of
high-level docs and
email them to you and Jukka and let's discuss.  Sooner
we get consensus, we
can get cooking !


Regards,

Peter Kasson


_____________________________________________________________________________________
Get more from the Web.  FREE MSN Explorer download :
http://explorer.msn.com

----- End forwarded message -----


=========================================
This mail sent through Sinclair's WebMail
      http://mail.sinclair.net

[Ijsql-devel] re: tasks

[Glen K. <gl...@ho...>]

>Cool.  I have Oracle and Mysql on Linux, and InstantDB >on Linux and 
>Windows.
>Sounds like we have a good range if things -- you just >about have it all!
>Anyone else have any other dbms or platforms available >for test?

I have Sybase 11.5 running under WindowsNT and SQL Server 7 running under 
Windows 2000 at work.


_____________________________________________________________________________________
Get more from the Web.  FREE MSN Explorer download : http://explorer.msn.com

[Ijsql-devel] Re: Tasks and the like

[William G. <ww...@ts...>]

Hello, Peter --

> Yes, the cross-db stuff, xml, metadata and the like are probably a lot for
> the first release.

Well, the expansion of the metadata querying (task 3) should be easy; I've
already been thinking on that, and will add it in shortly.  Jukka already
has the code for switchable multiple db connections.  What other "major"
function or functions do you think we should target for initial release?

> I would like to see code generation as well, and possibly options like
pool
> managers ... etc., but certainly for v.2

Once we define what's in this release, let's rough out a release list for
the next couple of versions.

> I tried out the gui code in the CVS project, but only got the connect
panel.
>   The code looks like it has a JTree and the like, but could not get it up
> and running ... have you ?

Not recently: I know that it does require a class from the borland jar file
that's also in cvs.  Did you get that & put it in the classpath?  I can try
to get it running myself soon, too.  Also, I can get the "author", my friend
Stefan, to give us a hand   ;-)

> Task distribution - how would this be done ?

Not totally sure.  I'd like to see if anyone has any areas they prefer to
work on.  One area I want to keep working on is the basic console version,
since that's what I originally wrote, and what I use day-to-day at my work.
I'm hoping that others will just make their preferences / interests known,
and we can go from there.

> I have 5+ databases at my office to work with, on Linux and NT (Oracle,
> SQL-Server, MySQL, Interbase (Inprise), JDataStore, MSAccess as well as
> other xBase type databases.  I can do some development on these as well as
> testing.

Cool.  I have Oracle and Mysql on Linux, and InstantDB on Linux and Windows.
Sounds like we have a good range if things -- you just about have it all!
Anyone else have any other dbms or platforms available for test?

> Should there be anything as elaborate as class diagrams, modeling and the
> like being done here?  I have all the tools necessary and would offer my
> services as documenter if others want to do upfront design or want to
lead.
> I can do the design of these things as well, but wonder if this is
overkill
> (at least a few high-level diagrams would be good I think).

A class diagram, basic design, and perhaps a message flow diagram, will be
very nice as we separate into a MVC architecture (assuming that's the
approach we use to separate view from core code: other architecture
suggestions, anyone?), and as we add the sort of things you and Jukka are
talking about.  I don't want us to go too "design-crazy", but don't want to
make the opposite mistake either.  Let's see if anyone else has any comments
about design, then we'll add some basic design tasks into the release tasks.

One thing I do want to do is get us to agree on some coding conventions.
I'd also like to go back and comment the code, and then require javadoc at
the beginning of each class and method.  This will make maintenance and
expansion much easier in the future ...

Thanks again for the input!  Anyone else have comments / ideas /
objections??

Regards,
Bill Graham

[Ijsql-devel] tasks for premier release

[William G. <ww...@ts...>]

My thoughts on tasks;  these need to be prioritized and pared down, as not
all of these should be "immediates".  Please comment, add, object, give
thoughts on priorities, etc.  My priority list is at the bottom.

MAIN ARCHITECTURAL STEP:
1) separate "engine" and presentation layers, perhaps using
Model-View-Controller architecture; the goal is to have presentation totally
decoupled from the core code, so that "pluggable" presentations are easy.

CORE CODE TASKS:
2) add stored procedure (CallableStatement) support.

3) Expand the metadata queries: right now the DatabaseMetaData queries don`t
accept any parameters, so you can only invoke those methods which do not
take args; enhance the code so that methods taking args can be invoked.

4) switchable connections to multiple db`s.  This was Jukka`s idea, and is
in code he sent me: Jukka, is it in cvs yet?

5) get rid of the hard-coded Class.forName(drivername) stuff at the
begining; I`m leaning toward putting the driver classnames into a properties
file so they can be read in and loaded.  The version of code that was
checked in to cvs has this, but it`s not been tested at all (compiles ...
;-)

6) look at exception handling: right now, the tool crashes if there`s a
SQLException.  it should just print a warning and continue on, especially if
it`s because of something like a typo in a query ...

7) Jukka and Peter: multi-db queries, two phase commits for premier release,
or is this further in the future?

8) decide on a package name; I still haven't heard from Sourceforge on using
"net.sourceforge.ijsql".

9) XML support, as Jukka and Peter have been discussing.

10) OQL and/or JDO integration: I think these can wait until a bit later on.

11) Glen's idea on tab-completion for column and tablenames.  I'm thinking
the base functionality for this goes in core ... for the console, it would
get implemented via tab completion, for the gui, via tab, and optionally via
a popup once you hit a period after a recognized tablename?

VIEW-ORIENTED TASKS:
12) Console view:
    a. decouple it from the core code
    b. add config settings  from the command line (similar to Oracle
SQL*Plus):
        1. column display lengths
        2. spooling output to a file
        3. spooling output tothe printer
        4. shell to an editor to edit complex sql, which will execute upon
exiting the editor

13) Swing gui view: adapt the Swing code in the CVS src/gui subdirectory to
use the iJSQL core code

14) Servlet and/or JSP view: do we want a defined, standard servlet or jsp
view, or do we just want the core code as pluggable as possible?  Or both?
;-)

----------------------------------------------

My thoughts on priority, not in any certain order:
Top Priority:  #1
Core Code Priorities: 3 (easy), 4(already done?), 5(already done?), 6, 7,
8(easy), 9
View Code Priorities: 12a, 12b1 (easy), 12b2 (easy), 13

Ok -- that's my list.  As you can see most if it is just reorganizing of
emails that have appeared on the list before.  If I've left out anyone's
ideas, I'm sorry: let me know, and we'll examine them and fit them in the
priorities for the premier or for a later release.

Once we've hashed this out, I'll put these in as tasks.  Also, be thinking
about what areas you would like to work on, so we can begin assigning tasks.

Thanks!!

Bill Graham

Re: [Ijsql-devel] Re: iJSQL list

[Jukka U. <juk...@vt...>]

Message Sun, 26 Nov 2000, Peter wrote:
> 
> I like the XML involvement, I have worked with it a bit, but not as much as 
> I would like - would you be using XML4J from IBM Alphaworks - it is really 
> quite good and free to distribute.
> 
> Depending on whether we use DOM or SAX, there are many options - SUN has 
> "JAX" as well, which is like SAX ... many options.
> 

I have worked little with XML4J and with Xerces also, but i think we can make
xml-parser like plugin. As far they use same DOM or SAX model this 
should be possible. I don't have make this kind of features but i have seem
some. 

Maybe first would be with XML4J and in version 2 we can xml-parser like 
plugin module.

> Exporting meta data, or extract data (queries ...) would be quite nice.
> 

I have done application which exports resultset to XML document with 
asp and I think should not be hard thing with java.


regards,

- Jukka -

Re: [Ijsql-devel] Re: iJSQL list

[Jukka U. <juk...@vt...>]

Wed, 22 Nov 2000, Peter wrote:
> 
> 2)  The more relevant communication I was referring to was to have 2 
> (possibly more) connections open and do the data migration, cross-db query 
> ... between 2 db's.  This does not require XA if doing query (data mining 
> eetc.) and possibly only 1 commit on db "x" where an update may be desired.
> 
> This should be quite simple to accomplish - just have 2 connections open and 
> represent this in the Swing model via 2 root nodes (each node representing a 
> db).  I have not looked at the Swing model yet, have you?
> 

No,  I am not very familiar with any gui programming except servlets. But this
souds good way do it. And if we make 1 root node and represent these 
connections in first child nodes, it would be easy export this data as XML
document. Or it does not matter if there are 2 root nodes in user interface but 
why make two model to represent same thing.

> 
> Would this also be desired - show data from a DB as well as meta-data in a 
> tree control or the like ?
> 

I think this would be good thing with export data and meta-data as xml-document.

What do you think about cross-db query? Something graphical query like 
MS Query or own SQL-layer over db's sql or ...

- Jukka -

Re: [Ijsql-devel] Re: iJSQL list

[Jukka U. <juk...@vt...>]

Sun, 19 Nov 2000, Willaim Graham wrote:
> 
> Quoting Peter Kasson <pk...@ho...>:
> 
> >
> > But, in response to your message - XA - what I was 
> thinking was this:
> >
> > 1)  Support 2-phase commit processing (ala XA), and 
> thus have 2+
> >     connections open to different databases and do 
> cross-database query
> >     and update transaction processing.
> >
> >     This would allow for data migration, 
> transformation (like SQL-Server
> >     Data Transformation Services) and the like.
> >

This is quite hard to do feature but very worth to research, i think.
Even simple data transfer between 2 db:s, without 2-phase commit
and complex data processing during transfer, might be useful feature.

- Jukka -

Re: [Ijsql-devel] Re: jSQL Topics

[Jukka U. <juk...@vt...>]

Sun, 19 Nov 2000, Bill wrote:
> Another great idea.  One more thing to go on the list ...   ;-)
> 
> Bill
> 
> ----- Original Message -----
> From: "Glen Koundry" <gl...@ho...>
> To: <Ijs...@li...>
> Sent: Saturday, November 18, 2000 10:51 AM
> Subject: [Ijsql-devel] Re: jSQL Topics
> 
> 
> > I think the previously mentioned features sound good.
> >
> >   The only thing I would like to add is maybe have an object name
> completion
> > feature that works something like filename completion in Bash or the
> > method/property completions in VB.  Basically, if the user was typing some
> > SQL code and they hit the TAB key it would search the current database for
> > and tables, procedures, etc. that match what was being typed and if so,
> > types it in automatically.
> >

Yes, i like this kind of things. They help me a lot, maybe you have
noticed number of typo ... :)

However, i think we should put focus to functinality like data migration, 
data transfer, different data sources, secrets of different jdbc-drivers and
so on, in iJSQL . Or maybe some of us start focusing user interface things and
some of us take things behind user interface.

- Jukka -

Re: [Ijsql-devel] Re: jSQL Topics

[William G. <ww...@ts...>]

Another great idea.  One more thing to go on the list ...   ;-)

Bill

----- Original Message -----
From: "Glen Koundry" <gl...@ho...>
To: <Ijs...@li...>
Sent: Saturday, November 18, 2000 10:51 AM
Subject: [Ijsql-devel] Re: jSQL Topics


> I think the previously mentioned features sound good.
>
>   The only thing I would like to add is maybe have an object name
completion
> feature that works something like filename completion in Bash or the
> method/property completions in VB.  Basically, if the user was typing some
> SQL code and they hit the TAB key it would search the current database for
> and tables, procedures, etc. that match what was being typed and if so,
> types it in automatically.
>
> Glen K
> Sa...@us...
>
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
> Share information about yourself, create your own public profile at
> http://profiles.msn.com.
>
> _______________________________________________
> Ijsql-devel mailing list
> Ijs...@li...
> http://lists.sourceforge.net/mailman/listinfo/ijsql-devel
>