🚀 go-pugleaf

Hello world,


We found the answer or problem on question number 1:
-------------------------------------------
We used the 'TIMESTAMP' SQL reserved word as a columnname
in one of our table definitions, aiai.
When making a query using this column as parameter,
Oracle was not able to complete the query.
Renaming the column in the table definition realy
did the trick.  It works...


BUT we still can't use the JDBC Explorer from any system with JBuilder 3
on it. Seems like the java-side on the Oracle Server is confused.
May be as a result of the 'TIMESTAMP' usage earlier......

Any help, or suggestions would still be greatly
appreciated !!!


Regards,


Bernard Stibbe (b.stibbe@nrsbenelux.nl)
Pim Klingens (p.klingens@nrsbenelux.nl)



Bernard Stibbe heeft geschreven in bericht
<932379122.21649.0.pluto.c3adeab5@news.demon.nl>...
>Hello world,
>
>We are developing some applications in Java and
>found some problems. To continue with the project
>we need some advise or solutions.
>
> We have two questions/issues:
>
>Question 1
>---------------
>We have a table in Oracle 8.0.4 that has 4 columns in its Primary Key.
>(3 Numbers and a Date). When using a QueryDataset (in JBuilder 3) on this
>table we are unable to insert a record at some point. We get a
>key-violation resolving the changes when we are sure the key of the to
>be inserted record is unique.
>
>(We have created a QueryResolver for this QueryDataSet and have set
>setUpdateMode(com.borland.dx.dataset.UpdateMode.KEY_COLUMNS);)
>
>When using the JDBC Explorer only two of the four columns we defined in
>the Primary Key are visible for this table!?!  In Oracle using SLQPlus we
>do see the Primary Keys as we defined them.
>We use the the thin JDBC clientdriver for JDK1.1.1
>
>Why and what is going on in the JDBC Explorer of Inprise !?!?
>
>Question 2
>---------------
>JDBC Explorer in JBuilder3 hangs when fetching table information (PK,
>IE, Columns) on Oracle Oracle 8.0.4 using the thin JDBC clientdriver for
>JDK1.1.1 or using an ODBC-JDBC bridge. (It has worked....)
>After killing the instance and posting open transactions on the Oracle
>database the JDBC explorere becomes 'alive' again.
>
>We are stuck!  Any help, or suggestions would be greatly
>appreciated !!!
>
>
>Regards,
>
>
>Bernard Stibbe (b.stibbe@nrsbenelux.nl)
>Pim Klingens (p.klingens@nrsbenelux.nl)
>
>
>
>