Please note that you must use extreme caution with mySQL: it did
not support transactions until very recently (v 3.23.6?), and even now you
must install an add-on product and specifically indicate that *each table*
should be transaction-safe when you create it. Since the default table
type is not transaction-safe, *you cannot allow JAWS to create tables for
you*, and that means this mapping is not very useful.
Because nearly all MySQL installations are not set up for
transactions, and J2EE depends on databases supporting transactions, we
strongly recommend that you consider another product (such as
PostgreSQL). If you are absolutely sure that everything is set up
correctly for transactions, and you manually create all tables that your
EJBs will use, then it should work, but again I would recommend mySQL only
as a last resort - if you make any mistakes in the configuration, you are
setting yourself up for data corruption.
Aaron
On Wed, 8 Nov 2000, Tobias Frech wrote:
> Hi mySQL users!
> As my new and tested mySQL type-mapping didn't make it into the new beta
> (Sebastien, how are you?) I'd like to post it here to make the live
> easier for all you guys who want to use mySQL. Tested with
> dbtest/AllTypes package.
>
> for [standard]jaws.xml:
>
> <type-mapping>
> <name>mySQL</name>
> <mapping>
> <java-type>java.lang.Short</java-type>
> <jdbc-type>SMALLINT</jdbc-type>
> <sql-type>SMALLINT</sql-type>
> </mapping>
> <mapping>
> <java-type>java.util.Date</java-type>
> <jdbc-type>DATE</jdbc-type>
> <sql-type>DATETIME</sql-type>
> </mapping>
> <mapping>
> <java-type>java.sql.Date</java-type>
> <jdbc-type>DATE</jdbc-type>
> <sql-type>DATETIME</sql-type>
> </mapping>
> <mapping>
> <java-type>java.sql.Time</java-type>
> <jdbc-type>TIME</jdbc-type>
> <sql-type>BIGINT</sql-type>
> </mapping>
> <mapping>
> <java-type>java.lang.Byte</java-type>
> <jdbc-type>TINYINT</jdbc-type>
> <sql-type>TINYINT</sql-type>
> </mapping>
> <mapping>
> <java-type>java.lang.Integer</java-type>
> <jdbc-type>INTEGER</jdbc-type>
> <sql-type>INTEGER</sql-type>
> </mapping>
> <mapping>
> <java-type>java.lang.Boolean</java-type>
> <jdbc-type>TINYINT</jdbc-type>
> <sql-type>TINYINT</sql-type>
> </mapping>
> <mapping>
> <java-type>java.lang.Object</java-type>
> <jdbc-type>JAVA_OBJECT</jdbc-type>
> <sql-type>BLOB</sql-type>
> </mapping>
> <mapping>
> <java-type>java.lang.Long</java-type>
> <jdbc-type>BIGINT</jdbc-type>
> <sql-type>BIGINT</sql-type>
> </mapping>
> <mapping>
> <java-type>java.lang.String</java-type>
> <jdbc-type>VARCHAR</jdbc-type>
> <sql-type>VARCHAR(255)</sql-type>
> </mapping>
> <mapping>
> <java-type>java.lang.Double</java-type>
> <jdbc-type>DOUBLE</jdbc-type>
> <sql-type>DOUBLE</sql-type>
> </mapping>
> <mapping>
> <java-type>java.lang.Character</java-type>
> <jdbc-type>CHAR</jdbc-type>
> <sql-type>CHAR</sql-type>
> </mapping>
> <mapping>
> <java-type>java.lang.Float</java-type>
> <jdbc-type>FLOAT</jdbc-type>
> <sql-type>FLOAT</sql-type>
> </mapping>
> <mapping>
> <java-type>java.sql.Timestamp</java-type>
> <jdbc-type>TIMESTAMP</jdbc-type>
> <sql-type>TIMESTAMP</sql-type>
> </mapping>
> </type-mapping>
>
> You'll find additional docu under bug #219 and #220
> (http://www.telkel.com/bugzilla/).
>
> Have phun.
>
> Tobias
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
