It's the configuration program for the database that creates the user, tables, constraints and data and so on. It would be much more effort on this to implement two connection functions and change the program than just before creating the user to say 'now Internal mode' and after 'now Oracle mode again'. Oracle mode is necessary for us to use the Oracle functions like TO_DATE that seem not to be available for INTERNAL mode. I'm using com.sap.dbtech.jdbcext.ConnectionPoolDataSourceSapDB as Driver to connect.
Mathias -----Original Message----- From: Zabach, Elke [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 07, 2004 2:16 PM To: Stoedtler, Mathias; [EMAIL PROTECTED] Subject: AW: RESOURCE NOT EXCLUSIVE and Oracle Mode Stoedtler, Mathias wrote: > > Ok, is it then somehow possible to switch in one JDBC session from > Internal to Oracle and reverse or has to connection to be closed and > reopened? By now I set the property with the Driver method > setSqlMode(...). > Sorry, but you want to tell us, that you have a JDBC-session/application doing this and that and by the way creating a database-user?!?! Oops, what kind of JDBC session is that? Usually users are created within SQLStudio, meaning online, typed in by the administrator of the database. Or the other way round: what kind of problem do you want to solve by creating a user 'on the fly'? Elke SAP Labs Berlin > Greets, > Mathias > > -----Original Message----- > From: Zabach, Elke [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 07, 2004 2:01 PM > To: Stoedtler, Mathias; [EMAIL PROTECTED] > Subject: AW: RESOURCE NOT EXCLUSIVE and Oracle Mode > > Stoedtler, Mathias wrote: > > > > Hello, > > > > Is there a way to create a user in SQLMode=Oracle and set the NOT > > EXCLUSIVE Option? > > > > CREATE USER myUsername PASSWORD myPassword RESOURCE NOT > > EXCLUSIVE > > > > works fine in INTERNAL mode. > > > > CREATE USER myUsername IDENTIFIED BY myPassword RESOURCE NOT > > EXCLUSIVE > > > > also works, but trying to connect twice with two at one time does not > > work then. > > > > The NOT EXCLUSIVE option will only work in internal mode. > As we say: we are compliant to an older Oracle-version, especially > compliant > to statements used in applications. The create user statement is > accepted, but several options in the end not read/ignored. In your case, > the RESOURCE NOT EXCLUSIVE is ignored, therefore the behaviour you saw, > is exactly the > expected and implemented one. > --> do the create user in the internal mode > > Elke > SAP Labs Berlin > > > > > Thanx and Greets, > > Mathias > > > > > > -- > > MaxDB Discussion Mailing List > > For list archives: http://lists.mysql.com/maxdb > > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
