ijsql-devel — development list for iJSQL

[Ijsql-devel] Re: iJSQL list

[Willaim G. <ww...@si...>]

Hi, Peter -- I'm cc'ing the list so they can see this  
(everyone: see quoted message from Peter below).  It's 
an awsome idea!  Maybe the work Jukka's done already on 
allowing multiple connections open to separate db's 
will help in moving this direction ...

I agree that it would be a *great* feature to have ...

Sorry you're having problems with the list ... I'm 
pretty new to Sourceforge, too, so don't have any real 
advice ... if it keeps going like that, you might 
consider putting in an email to support.  ALthough, I 
have two emails in to support and have not received a 
reply for weeks ...

Regards,
Bill Graham


Quoting Peter Kasson <pk...@ho...>:

> Bill,
>
> I can't get into the mailing lists and respond to 
messages.  It says that I
>
> have to log in and I am logged in.
>
> I am new to Source Forge and dont know if I am doing 
something wrong.
>
> 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.
>
> Just an idea.  I usually have to jump through hoops 
to get things done and
> this approach would be awesome.
>
> Peter
>
> 
________________________________________________________
_________________
> 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.
> 


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

[Ijsql-devel] Re: jSQL Topics

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

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.

Re: [Ijsql-devel] jSQL Topics

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

Hello, folks --

I had envisioned the defining of the featureset to be something that the
group would decide on.  I posted my list of desired features (which
included a few that Jukka had sent me) a bit earlier, and Jukka has
answered with comments, code, and expansion of some of the ideas.  I've
been sort of waiting for some more input from team members: comments,
critique, "that one's a bad idea because ...", additional ideas, etc.

So I'll ask again: does anyone else have any ideas about what sort of
features they would like to see, or what directions they would like to
see the project going?  If noone else responds, I'll try to formalize
the goals and create tasks from them.

Regards,
Bill Graham

Peter Kasson wrote:
> 
> Group,
> 
> I would like to see a list of features, past present or future, that this
> product is envisioned to deliver on before posting more suggestions or
> coding effort.

[Ijsql-devel] jSQL Topics

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

Group,

I would like to see a list of features, past present or future, that this 
product is envisioned to deliver on before posting more suggestions or 
coding effort.

Regards,

Peter

_________________________________________________________________________
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.

Fwd: Re: [Ijsql-devel] ToDo list brainstorming

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

Forwarding to list; I think this only went to me ...
Regards,
Bill G.

----- Forwarded message from Jukka Uusisalo
<juk...@vt...> -----
Date: Tue, 14 Nov 2000 20:29:52 +0200
From: Jukka Uusisalo <juk...@vt...>
Reply-To: juk...@vt...
Subject: Re: [Ijsql-devel] ToDo list brainstorming
To: william graham <ww...@ts...>


>
> 5) Separating the "engine" code from the presentation
logic; this
> obviously goes hand in hand with #1 above, and will
also allow the main
> code's use in servlets, jsp, etc.  Maybe servlet
and/or jsp interfaces
> will become a feature as well?
>

I think servlet/jsp -interface would be usefull. Just
put iJSQL servlet to
your intranet server and let your team mates use it.

> 6) Switchable connections to multiple db's.  This was
Jukka's idea, and
> he's working on this now; it'll be sort of like
virtual consoles: I
> might have a connection open to an Oracle db, then be
able to switch to
> another thread which is handling a connection to
MySQL, etc.  Jukka,
> jump in and correct me if I've misunderstood this
feature ...
>

You have understood this point correctly and I think you
have received
some code for this features.

>
> 8) bug fixes, as soon as we get around to logging
bugs.  One irritating
> one that I know of is that 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 am not sure but propably we will need some own
exception classes
to hadling exceptions and decide which are fatal and
which are just
worth of error messages.

> 9) Integrating in or writing an OQL (Object Query
Language)
> parser/interpreter, so that the tool will be able to
handle non-jdbc
> object repositories (such as the ObJectBridge project
also on
> Sourceforge).
>

That is intresting point. I like to see this kind of
stuff more because Object
mapping to rdb is ugly work. Little bit same thing, Does
somebody know
JDO (Java Data Objects)?


Regards,

- Jukka -

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


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

[Ijsql-devel] ToDo list brainstorming

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

Here's a list of features that I'm thinking of; quite a few are the
result of some emails traded between Jukka and myself:

1) Swing gui as an alternative to the console; a friend of mine has
donated some Swing code from a nice gui db browser he wrote, so we can
start with that; it's in cvs now, in the gui sibdirectory.

2) Adding some config settings from the command line, ala Oracle's
Sql*Plus (i.e., setting column display lengths, directions to spool
output to a file / print que, ability to shell to an editor to edit
complex sql, then have it execute upon exiting the editor, etc.)

3) Adding stored procedure (CallableStatement) support

4) Expanding 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 (it'll be simple to implement the args)

5) Separating the "engine" code from the presentation logic; this
obviously goes hand in hand with #1 above, and will also allow the main
code's use in servlets, jsp, etc.  Maybe servlet and/or jsp interfaces
will become a feature as well?

6) Switchable connections to multiple db's.  This was Jukka's idea, and
he's working on this now; it'll be sort of like virtual consoles: I
might have a connection open to an Oracle db, then be able to switch to
another thread which is handling a connection to MySQL, etc.  Jukka,
jump in and correct me if I've misunderstood this feature ...

7) getting 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 ...   ;-)

8) bug fixes, as soon as we get around to logging bugs.  One irritating
one that I know of is that 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 ...

9) Integrating in or writing an OQL (Object Query Language)
parser/interpreter, so that the tool will be able to handle non-jdbc
object repositories (such as the ObJectBridge project also on
Sourceforge).

10) we need a package name, as Jukka pointed out in his first email to
me.  I'm still not sure how that's going to work: if we do the standard
thing and reverse the domain name, it would be "net.sourceforge.ijsql",
but I don't know if we're allowed to use the sourceforge name.  I have
an inquiry in with support to get an answer.  If we don't get that
permission, we can use my domain, curiousmuse.com.

Anyone else have ideas?  Peter, you mentioned XA ...