Paul Mason wrote:
Erm. I don't wish to be rude but I find it hard to take this objection
seriously.
sed 's/;/\\g/' ingres_schema.sql > other_schema.sql
sed 's/\\g/;/' other_schema.sql > ingres_schema.sql
Sorry but this is way way down the list of things to worry about when
porting from one DBMS (or MySQL) to another. Not least non-standard
SQL syntax, never mind how it's executed.
There's been a lot of work, and continues to be, to make it easier to
port to Ingres from other DBMSs - but this really is trivial.
And if you really don't like it, terminal monitor is probably one of
the easier things to modify. Or you could write your own. Or you could
use a JDBC or ODBC one.
(chuckles) Yes - all true (indeed I had previously written a simple JDBC
client which does what you suggest for that reason). And yes I (or you)
can work around all these things, but the issue is not really about that
is it?
I guess I was trying to point out that the behavior of (say) 'sql' is a
difference that adds no value - the first impression people gain of a
database product is often via the command line client, and I'm hinting
that unusual or unexpected behavior may cause a (completely unnecessary)
negative impression. Err ... you *do* want to make is easy for people to
start using Ingres and enjoy it - right?
In fact adapting 'sql' to behave in the way I mention is probably a
perfect task for a keen community volunteer (*provided* there
encouragement) anyone could do this!
Cheers
Mark
P.s : I don't have any time to look at it now - but might next year...
(I'm actually developing for Postgres at the moment)
_______________________________________________
Users mailing list
[email protected]
http://lists.ingres.com/mailman/listinfo/users
