You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by ma...@apache.org on 2003/02/05 00:10:49 UTC
cvs commit: db-ojb/xdocs platforms.xml
mattbaird 2003/02/04 15:10:49
Modified: xdocs platforms.xml
Log:
update to platform docs
Revision Changes Path
1.7 +14 -14 db-ojb/xdocs/platforms.xml
Index: platforms.xml
===================================================================
RCS file: /home/cvs/db-ojb/xdocs/platforms.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- platforms.xml 21 Dec 2002 18:57:19 -0000 1.6
+++ platforms.xml 4 Feb 2003 23:10:48 -0000 1.7
@@ -11,7 +11,7 @@
<section name="how to use OJB with a specific relational database">
<p>
OJB has been designed to smoothly integrate with any relational
-database that provides JDBC support. OJB uses only JDBC 1.0 API calls
+database that provides JDBC support. OJB can be configured to use only JDBC 1.0 API calls
to avoid problems with restrictions of several JDBC drivers.<br/>It
uses a limited SQL subset to avoid problems with restrictions of
certain RDBMS. This design allows to keep the OJB code generic and
@@ -216,19 +216,19 @@
You can choose one out of the predefined profiles:
<source>
# With the 'profile' property you can choose
-# the RDBMS platform OJB is using implemented profiles:
-profile=hsqldb
-#profile=mssqldb
-#profile=mssqldb-JNet
-#profile=mssqldb-Opta2000
-#profile=mysql
-#profile=db2
-#profile=oracle
-#profile=msaccess
-#profile=postgresql
-#profile=informix
-#profile=sybase
-#profile=sapdb
+# the RDBMS platform OJB is using implemented profiles:<br/>
+profile=hsqldb<br/>
+#profile=mssqldb-JSQLConnect<br/>
+#profile=mssqldb-Opta2000<br/>
+#profile=mssqldb-ms<br/>
+#profile=mysql<br/>
+#profile=db2<br/>
+#profile=oracle<br/>
+#profile=msaccess<br/>
+#profile=postgresql<br/>
+#profile=informix<br/>
+#profile=sybase<br/>
+#profile=sapdb<br/>
</source>
</p>
<p>