Thorbjoern Ravn Andersen <nospam0000@unixsnedkeren.dk> wrote:
> per.ronne@invalid.dk (Per Rønne) writes:
>
> > Hvis man hver dag rigtig mange gange starter op i emacs, så bliver det
> > nu besværligt. Og det vil man komme til, hvis man bruger den som
> > standardeditor, og dermed bruger den hver gang man skal skrive eller
> > modificere noget i bufferen i eksempelvis Oracles sql*plus eller
> > PostgreSQLs psql.
> emacsclient.
Hvilket betyder?
> > > >
http://www.oracle.com/start/apple/intro.html?src=1439096&Act=5
> > > Jep. Der er intet skrevet i Java med :( Det gør det lidt mere bøvlet.
> > Java? Bruger du da ikke almindelig C eller C++?
> Alle Oracles nye smarte vaerktoejer er skrevet i Java. Ingen af disse
> foelger med.
Man kan særskilt downloade følgende filer:
MacOSX_8171.cpio
og:
jdbc_thin_9_0_1
Om sidstnævnte følger der en LæsMig fil med, med følgende indhold:
Oracle JDBC Drivers Developer's release 9.0.1 README
====================================================
Driver Version
--------------
Only the Thin Driver is supported in the 9.0.1 Developer's release:
- JDBC Thin Driver 9.0.1
100% Java client-side JDBC driver for use in Java applets and
applications.
For complete documentation, please refer to "JDBC Developer's Guide
and Reference". The JDK 1.2.x Driver has been certed with JDK 1.3.x
on MAC OS 10
Contents Of This Release
------------------------
The [ORACLE_HOME]/jdbc/lib directory contains:
- classes111.zip & classes111.jar
Classes for use with JDK 1.1.x. It contains the JDBC driver
classes except classes necessary for NLS support in Object and
Collection types.
- nls_charset11.zip & nls_charset11.jar
NLS classes for use with JDK 1.1.x. It contains classes necessary
for NLS support in Object and Collection types.
- classes111_g.zip & classes111_g.jar
Same as classes111.zip, except that classes were compiled with
"javac -g" and contain tracing information.
- classes12.zip & classes12.jar
Classes for use with JDK 1.2.x. It contains the JDBC driver
classes except classes necessary for NLS support in Object and
Collection types.
- nls_charset12.zip & nls_charset12.jar
NLS classes for use with JDK 1.2.x. It contains classes necessary
for NLS support in Object and Collection types.
- classes12_g.zip & classes12_g.jar
Same as classes12.zip, except that classes were compiled with
"javac -g" and contain tracing information.
In general, <file>.zip and <file>.jar are identical except for the
format of the archive. Both the .zip and .jar formats are provided.
Note that most of the classes pertaining to specific character sets
support in Oracle Object and Collection types are separated from the
basic zip/jar files. These NLS classes are packaged into the
extension zip/jar files. This allows the user to include the NLS
classes only if necessary. Please refer to the "NLS Extension Zip
Files (for client-side only)" section for further details.
[ORACLE_HOME]/jdbc/doc/javadoc.tar contains the JDBC Javadoc. This
release contains a beta release of the Javadoc files for the public
API of the public classes of Oracle JDBC.
NLS and NLS Extension Zip/Jar Files (for client-side only)
----------------------------------------------------------
The JDBC Server-side Internal Driver provides complete NLS support.
It does not require any NLS extension zip/jar files, nls_charset*.*.
Discussions in this section do not apply to the JDBC Server-side
Internal Driver. You can skip this section if you only use the
Server-side Internal Driver.
The basic zip/jar files (classes111.zip, classes111.jar,
classes12.zip and classes12.jar) contain all the necessary classes
to provide complete NLS support for:
- Oracle Character sets for CHAR/VARCHAR/LONGVARCHAR/CLOB type data
that is not retrieved or inserted as a data member of an Oracle 8
Object or Collection type.
- NLS support for CHAR/VARCHAR data members of Objects and
Collections for a few commonly used character sets. These
character sets are: US7ASCII, WE8DEC, WE8ISO8859P1 and UTF8.
Users must include the appropriate extension zip in their CLASSPATH
if utilization of other character sets in CHAR/VARCHAR data members
of Objects/Collections is desired. It is important to note that
extension zip files are large in size due to the requirement of
supporting a large number of character sets. Users may choose to
include only the necessary classes from the extension zip/jar file.
To do so, users can first un-pack the extension zip/jar file, and
then put only the necessary classes in the CLASSPATH. The character
set extension class files are named in the following format:
CharacterConverter<OracleCharacterSetId>.class
where <OracleCharacterSetId> is the hexadecimal representation of the
Oracle character set id of the corresponding character set.
In addition, users can also include internationalized Jdbc error
message files selectively. The message files are included in
classes*.* with the name oracle/jdbc/dbaccess/Messages_*.properties.
-----------------------------------------------------------------------
Installation
------------
Please do not try to put multiple versions of the Oracle JDBC drivers
in your CLASSPATH. The Oracle installer installs the JDBC Drivers in
the [ORACLE_HOME]/jdbc directory.
Setting Up Your Environment
---------------------------
On MAC OS 10
- Add [ORACLE_HOME]/jdbc/lib/classes111.zip and
[ORACLE_HOME]/jdbc/lib/nls_charset11.zip to your CLASSPATH.
(Add classes12.zip and nls_charset12.zip if JDK 1.3.x is used.)
Some Useful Hints In Using the JDBC Drivers
-------------------------------------------
Please refer to "JDBC Developer's Guide and Reference" for details
regarding usage of Oracle's JDBC Drivers. This section only offers
useful hints. These hints are not meant to be exhaustive.
These are a few simple things that you should do in your JDBC program:
1. Import the necessary JDBC classes in your programs that use JDBC.
For example:
import java.sql.*;
import java.math.*;
2. Register the Oracle driver before before calling other JDBC APIs.
(This is not needed if you are using the JDBC Server-side Internal
Driver because registration is done automatically in the server.)
To register the Oracle driver, make sure the following statement
is executed at least once in your Java session:
DriverManager.registerDriver(
new oracle.jdbc.OracleDriver());
3. Open a connection to the database with the getConnection call.
Different connection URLs should be used for different JDBC
drivers. The following examples demonstrate the URL for the
thin driver.
For the JDBC Thin Driver:
Connection conn = DriverManager.getConnection(
"jdbc:oracle:thin:@<database>",
"my_user", "my_password");
where <database> is either a string of the form
<host>:<port>:<sid> or a SQL*net name-value pair.
New Package oracle.jdbc
-----------------------
Beginning in Oracle 9i, the Oracle extensions to JDBC are captured in
the package oracle.jdbc. This package contains classes and interfaces
that specify the Oracle extensions in a manner similar to the way the
classes and interfaces in java.sql specify the public JDBC API.
Your code should use the package oracle.jdbc instead of the package
oracle.jdbc.driver used in earlier versions of Oracle. Use of the
package oracle.jdbc.driver is now deprecated, but will continue to be
supported for backwards compatibility.
All that is required to covert your code is to replace
"oracle.jdbc.driver" with "oracle.jdbc" in the source and
recompile. This cannot be done piecewise. You must convert all classes
and interfaces that are referenced by an application. Conversion is
not required, but is highly recommended. Future releases of Oracle may
have features that are incompatible with use of the package
oracle.jdbc.driver.
The purpose of this change in to enable the Oracle JDBC drivers to
have multiple implementations. In all releases up to and including
Oracle 9i, all of the Oracle JDBC drivers have used the same top level
implementation classes, the classes in the package
oracle.jdbc.driver. By converting your code to use oracle.jdbc, you
will be able to take advantage of future enhancements that use
different implementation classes. There are no such enhancements in
Oracle 9i, but there are plans for such enhancements in the future.
Additionally, these interfaces permit the use of some code patterns
that are difficult to use when your code uses the package
oracle.jdbc.driver. For example, you can more easily develop wrapper
classes for the Oracle JDBC classes. If you wished to wrap the
OracleStatement class in order to log all SQL statements, you could
easily do so by creating a class that wraps OracleStatment. That class
would implement the interface oracle.jdbc.OracleStatement and hold an
oracle.jdbc.OracleStatement as an instance variable. This wrapping
pattern is much more difficult when your code uses the package
oracle.jdbc.driver as you cannot extend the class
oracle.jdbc.driver.OracleStatement.
Once again, your code should use the new package oracle.jdbc instead
of the package oracle.jdbc.driver. Conversion is not required as
oracle.jdbc.driver will continue to be supported for backwards
compatibility. Conversion is highly recommended as there may in later
releases be features that are not supported if your code uses
oracle.jdbc.driver.
Known Problems/Limitations In This Release
------------------------------------------
The following is a list of known problems/limitations:
1. Only the Thin driver is supported in the MAC OS 10
Environment.
--
Cand.scient. Per Erik Rønne
Frederikssundsvej 308B, 3. tv.
DK-2700 Brønshøj
Tlf + fax 38 89 00 16, mobil 28 23 09 92