ijsql-devel

[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] 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] 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

[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] 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