Paul Mason wrote:
Then what started to happen was a focus on GUI tools. So we got Visual
DBA and Visual Manager and so on. There was a general feeling that you
didn't want someone's first experience to be character based tools.
They looked and felt out of date. (Except to those of us happily using
them but we were generally old hands who knew how to set up things.)
So I think putting "how to set up TERM_INGRES" into the Getting
Started Guide would have been not the done thing at that point.
Then Linux started to become popular and a version of Ingres was
released for it. Which worked fine if you connected using one of the
terminal emulators that had always worked. If not then there were some
instructions in the Release Notes, but not the GSG for reasons
mentioned above. You see, up until that point the character based
stuff hadn't changed for years - because no-one was logging on
directly to unix hardware any more.
Anyway - there are reasons why we got where we are today - not that
that necessarily makes things any better. As for "it's an open source
project right?" well that's a whole different discussion and one I'm
not going to get into now.
This reminds me of something that came to mind when first installing
Ingres. There seems to be a need for a basic command line client that
works similarly to (Postgres) 'psql' or (Mysql) 'mysql' i.e:
1/ No terminal weirdness
2/ SQL command terminator ';' (or better - chooseable) [1]
3/ Command line re-entry (readline or libedit)
The current 2 that come out of the box (dbaccess and sql) are either too
fiddly (dbaccess) or too basic (sql).
Cheers
Mark
[1] AFAICS sql will only use '\n' as a command terminator - but I was
not able to find any doco about *if* it could be configured....so I may
have that point wrong :-)
_______________________________________________
Users mailing list
[email protected]
http://lists.ingres.com/mailman/listinfo/users