I think that's actually a fair point Mike.

Ultimately Terminal Monitor is not a high level language like Perl, C etc. So there is little point giving it lots of conditionals, those things are better done by a higher level language. That being said I still think that TM can stand lots of improvements, for example (off the top of my head):
1. Report writer like formatting specification.
2. Merging all the capabilities of ABF procedures into normal SQL procedures.

Marty

-----Original Message-----
From: Mike Leo [mailto:mleo (AT) kettleriverconsulting (DOT) com]
Sent: 26 March 2011 02:41
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] FW: Ingres command line client - vertical output?

Grrr .... I shouldn't have used thqt example!!!!!

It was CONTRIVED. CONTRIVED.

The point was, my terminal monitor used "markers" that would allow certain statements to fail
and the script would continue.

It also implemented conditionals, allowing me to terminate execution (with an error) if
a certain condition occurred.

What just dawned on me is that if the terminal server had all the things that I put in to
mine back in the mid-90's, I would probably still use Perl DBI/DBD.

So I TAKE IT ALL BACK!!!!!!! Leave the minimalist terminal monitor alone.

Use PERL.

Mikey

On Mar 25, 2011, at 9:02 PM, James K. Lowden wrote:



_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres

Martin Bowes wrote:

Especially for dates. We can use SET DATE_FORMAT in recent releases but
that's not sufficiently versatile as it stands, probably because it also
controls the acceptable input formats as well as the output format.

I'd settle for being able to declare "module global" temporary tables in
DBPs.

There was once talk of embedding OpenROAD in the server. I'm sure all
the OpenROADies would have liked that. In principle it would be a quick
way to add new data types and scalar functions. In practice I imagine
it would be a quick way to make a mess.

--
Roy

UK Ingres User Association Conference 2011 will be on Tuesday June 7 2011.
Register at http://www.regonline.co.uk/ukiua2011

Actually on reflection....
If I can get conditionals in terminal monitor... why the hell not? Whether or not I use them is really up to me. Just like using arrays in BASH, where I think to myself, if I have to use arrays in a shell script perhaps I'd be better off writing a Perl program.

Also Geraint tells me that he's looked at importing the Report Writer formatting into Terminal Monitor and he thinks it should be an achievable goal for the code sprint. I'm sure that with sufficient bribery (measured in pints) that he could be persuaded to have a crack at it.

Marty

-----Original Message-----
From: Roy Hann [mailto:specially (AT) processed (DOT) almost.meat]
Sent: 27 March 2011 11:28
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] FW: Ingres command line client - vertical output?

Martin Bowes wrote:

Especially for dates. We can use SET DATE_FORMAT in recent releases but
that's not sufficiently versatile as it stands, probably because it also
controls the acceptable input formats as well as the output format.

I'd settle for being able to declare "module global" temporary tables in
DBPs.

There was once talk of embedding OpenROAD in the server. I'm sure all
the OpenROADies would have liked that. In principle it would be a quick
way to add new data types and scalar functions. In practice I imagine
it would be a quick way to make a mess.

--
Roy

UK Ingres User Association Conference 2011 will be on Tuesday June 7 2011.
Register at http://www.regonline.co.uk/ukiua2011


_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres

Martin Bowes wrote:

Indeed.

I know you and Geraint know about the tm macros and branching, but for
anyone who doesn't, take a look at the Quel manual. They're not
documented in the SQL manual but tm is tm. Or rather, it's sql. (Or
quel.)

http://docs.ingres.com/ingres/10.0/q...monitor-macros

http://docs.ingres.com/ingres/10.0/q...2198-branching

I ain't saying the syntax is intuitive...

I'm sure the Benevolent Czarina won't object if I pass a hat round on
the day.

:-)

--
Roy

UK Ingres User Association Conference 2011 will be on Tuesday June 7 2011.
Register at http://www.regonline.co.uk/ukiua2011

James K. Lowden wrote:

The expected outcome was for the named table not to exist. It doesn't
exist. So the "error" you might be catching is a typo in the
table name or a missing schema name. Do you expect to have an error
reported when there's a typo in the name of the table you create? How
about when you use DROP TABLE IF EXISTS and there's a typo in the
table name?

Getting an error when you attempt to drop a table that doesn't exist is
inconsistent and presumptuous.

Those are true observations but not proof that attempting to drop a
table that doesn't exist is an error in your code.

--
Roy

UK Ingres User Association Conference 2011 will be on Tuesday June 7
2011.
Register at http://www.regonline.co.uk/ukiua2011

Roy Hann wrote:

Sorry about the double posting; I don't know how that happened.

--
Roy

UK Ingres User Association Conference 2011 will be on Tuesday June 7 2011.
Register at http://www.regonline.co.uk/ukiua2011

I hope there will be no drinking from hats. Please, let's be civilised.


--
geraintjones

Slippers?

-----Original Message-----
From: Ingres Forums [mailto:info-ingres (AT) kettleriverconsulting (DOT) com]
Sent: 28 March 2011 11:37
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] FW: Ingres command line client - vertical output?


I hope there will be no drinking from hats. Please, let's be civilised.


--
geraintjones


_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres