[teiid-users] [teiid-dev] Alternative scripting envrionment for AdminShell

[Steven Hawkins]

It doesn't seem like we have yet reached a consensus, but it does seem like:
1. people do like having a SQL oriented interactive command line tool.
2. most see the SQL functionality as separable from the admin/test.

Agreed?

I'd also like to relay a local discussion with Ramesh.  His basic premise was that if we decouple the admin/test aspects and promote an alternative command line SQL tool, then we should just forgo offering any built-in environment for administrative scripting.  In this case the approach would be to just document which class/classes could be imported (as shown in the previous Groovy example with the static import of AdminShell methods) into your java scripting language of choice.

----- Original Message -----
From: "Ramesh Reddy" <rareddy at redhat.com>
To: "John Doyle" <jdoyle at redhat.com>
Cc: "Steven Hawkins" <shawkins at redhat.com>, "teiid-users" <teiid-users at lists.jboss.org>, "teiid-dev" <teiid-dev at lists.jboss.org>, "Paul Nittel" <pnittel at redhat.com>
Sent: Tuesday, April 13, 2010 9:41:49 AM GMT -06:00 US/Canada Central
Subject: Re: [teiid-users] [teiid-dev] Alternative scripting envrionment for AdminShell

On Tue, 2010-04-13 at 09:27 -0400, John Doyle wrote:
> You nailed my concern Steve.  I've never actually used AdminShell for
> admin tasks, I use it like 
> SQL*PLUS.  I think there are probably more reasons to separate these
> concerns than to combine them.  I haven't looked at either of the two
> tools you linked to, but if we can validate that one of them works
> well enough then I think that should be sufficient for a query tool
> for Teiid.
> 
> I think the added verbosity of the groovy solution is more acceptable
> for an admin tool than for a query tool, and is worth it given the
> added capabilities that multiple connections offer. 

Please take integration test and write using this tool, and you will see
the reasons for this added verbosity.

Ramesh..