ijsql-devel

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

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

[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