As a separate tool it is focused enough to support features such as sql command completion
and other much beyond what we can offer :)
Integration with Groovy isn't really the right path coming from this direction. You
would rather see us support more functionality through sql, like the old admin vdb - which
could be added back easily with the reduced admin logic and admin objects that map to xml
(sqlxml). We should even support in line definition of procedures, which may require
changes in the tool to support, but would mitigate the need for introducing another
language.
----- Original Message -----
From: "Ramesh Reddy" <rareddy(a)redhat.com>
To: "Steven Hawkins" <shawkins(a)redhat.com>
Cc: "Paul Nittel" <pnittel(a)redhat.com>, "teiid-users"
<teiid-users(a)lists.jboss.org>, "teiid-dev"
<teiid-dev(a)lists.jboss.org>
Sent: Monday, April 12, 2010 6:31:27 PM GMT -06:00 US/Canada Central
Subject: Re: [teiid-dev] Alternative scripting envrionment for AdminShell
On Mon, 2010-04-12 at 17:22 -0400, Steven Hawkins wrote:
Even with those limitations I understand that it does serve as a
reasonable approximation to something like SQL*Plus. I question
whether we need to support specialized tooling for this purpose (over
just using what's available in Groovy). We could just as well promote
the use of
http://sourceforge.net/projects/sqlshell/ or the older
http://henplus.sourceforge.net/.
As separate tool it seems verbose and fragmented offering. If we can
integrate these tools into groovy or add missing features as pulgins
into these tools seems like the right path. The both tools above have
their own shell environments, integrating with them or into groovy, both
may be challenging.
Henplus, seems to have extensive features, and seems to have the
simultaneous name based connections, so it definitely gets my vote if we
decide go this route.
Ramesh..