| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5039.1 | HAVE WE TO BUG THAT ? | CHSR36::LCONS | | Mon Feb 24 1997 08:38 | 0 |
| 5039.2 | | NOVA::SMITHI | Don't understate or underestimate Rdb! | Mon Feb 24 1997 10:57 | 3 |
| What is the problem? You don't really show an example.
Ian
|
| 5039.3 | No � on SQL command line | chsr38.ch.oracle.com::ROHR | The Packers did it! | Mon Feb 24 1997 11:06 | 7 |
| The problem is that while you can construct a '�' onthe OS level you
can't do a SQL> insert into bla value '�'. You just can't enter that.
On the SQL command line no � shows up.
Or maybe it's just us who don't succeed. If someone could tell us.
Tried from PC and AXp Station.
/Regina
|
| 5039.4 | | ukvms3.uk.oracle.com::PJACKSON | Oracle UK Rdb Support | Mon Feb 24 1997 11:24 | 8 |
| > The problem is that while you can construct a '�' onthe OS level you
> can't do a SQL> insert into bla value '�'. You just can't enter that.
> On the SQL command line no � shows up.
It works for me using a decterm session on a Vaxstation.
The sequence I used was <Compose & space>o"
Peter
|
| 5039.5 | | CHSR36::JSUBRI | Focus on Open/Rdb++ | Mon Feb 24 1997 11:29 | 8 |
| well, the editor under SQL workaround this problem.
Maybe a variable's environment ?
On Motif, cut and paste at "SQL> prompt" shrink 8 bits chars
'�' become '' .
/Jean-Luc
|
| 5039.6 | <Compose & space>o" ? | CHSR36::LCONS | | Mon Feb 24 1997 11:42 | 5 |
| How can i do that ?
Also for �,�,�,�,�...
As Jean-Luc said, the EDIT workaround is ok, perhaps have we missed something...
Louis
|
| 5039.7 | | ukvms3.uk.oracle.com::PJACKSON | Oracle UK Rdb Support | Mon Feb 24 1997 12:13 | 17 |
| >How can i do that ?
Do you have a compose key? On my VAXstation 3100 if I press compose and
space together the compose light comes on. Then I can enter characters
not on the keyboard by entering the correct sequence.
o" = � e' = � etc.
SQL> insert into t3(c1) values ("��������ƥ�");
%SQL-I-DEPR_FEATURE, Deprecated Feature: " used instead of ' for string
literal
1 row inserted
SQL> select * from t3;
C1
��������ƥ�
1 row selected
Peter
|
| 5039.8 | Are you on Unix as well? | chsr38.ch.oracle.com::ROHR | The Packers did it! | Tue Feb 25 1997 02:49 | 8 |
| Peter,
compose works fine when I have a Decterm on a VMS system, but not on the
Unix one. Must be something in the setup. Like STTY settings or so?
Would you mind sharing your Unix session setups?
Thanks,
Regina
|
| 5039.9 | | ukvms3.uk.oracle.com::PJACKSON | Oracle UK Rdb Support | Tue Feb 25 1997 05:35 | 10 |
| > -< Are you on Unix as well? >-
No, I had missed that.
Compose does not work for me on UNIX sessions. Probably it is the
character set in use for the terminal. VMS defaults to using the DEC
Multinational chracter set. I don't know UNIX well, but I would guess
it defaults to ASCII.
Peter
|
| 5039.10 | | chsr38.ch.oracle.com::CONS | Oracle Rdb support Switzerland | Tue Feb 25 1997 09:04 | 26 |
| Hello,
It is working fine on SQLPLUS:
SQL> select * from scott.emp where ename = '���';
no rows selected
Also on Rdb7/Unix with EDIT
SQL> edit
select * from employees where employee_id = '���';
~
~
:wq
Do you wish to execute these commands (Yes)?
select * from employees where employee_id = '���';
0 rows selected
SQL>
The only thing that is not working is typing these 8-bit characters directly in
a Sql Rdb Unix session.
On the same terminal it is working on SQLPLUS and SQL RDB with EDIT.
Louis
|
| 5039.11 | try RDB_NOLINEDIT | NOVA::HERRE | | Wed Mar 12 1997 16:37 | 8 |
| The code that allows line editting of the SQL command line
appears to prevent 8 bit characters from being accepted.
After playing with my shell to make sure that I could get
8 bit characters to work there, I put the line
RDB_NOLINEDIT T
in my .dbsrc file. After that, I could use the compose key
to enter the characters.
|
| 5039.12 | That works | CHSR38::ROHR | The Packers did it! | Thu Mar 13 1997 03:05 | 4 |
| That works,
thanks a bunch!
Regina
|
| 5039.13 | RDB_NOLINEDIT T in .dbsrc | CHSR36::JSUBRI | Focus on Open/Rdb++ | Thu Mar 13 1997 03:10 | 4 |
| Great
Thanks
/Jean-Luc
|
| 5039.14 | What is 'on'? | CHSR38::ROHR | The Packers did it! | Thu Mar 13 1997 03:20 | 11 |
| It is not really evident to assume a relationship between this
parameter and the 8 bit characters.
Also, the Rdb7 Unix Installation and COnfiguration file says that the
installation default of RDB_NOLINEDIT is 'on'. Should that mean TRUE?
If yes, either the doc or Rdb7 on Unix are wrong.
Our rdb.conf is empty.
/Regina
|
| 5039.15 | doc error | NOVA::HERRE | | Thu Mar 13 1997 13:20 | 11 |
| I think the doc is wrong. The description for RDB_NOLINEDIT in
the doc is what I would expect if the variable was RDB_LINEDIT;
the default value in the doc does agree with the description, though.
The relationship between the line editor and 8 bit characters should
probably be documented. Some of the line editor commands use the
escape key as a prefix, which generates a character with the eighth
bit set which is then mapped to a line editor function. Whenever the
line editor sees the eighth bit set, it assumes that the input
character is an edit command.
|
| 5039.16 | Who bugs | CHSR38::ROHR | The Packers did it! | Fri Mar 14 1997 03:08 | 2 |
|
You bug - I bug - doc group listens?
|
| 5039.17 | | 6184::JSUBRI | Focus on Open/Rdb++ | Fri Mar 14 1997 06:43 | 3 |
| I already QARed this in rdb_70 few weeks ago
/Jean-Luc
|
| 5039.18 | | WEORG::GREMBOWICZ | | Fri Mar 14 1997 09:47 | 6 |
| >You bug - I bug - doc group listens?
Yep, we hear you.
|