[
http://jira.jboss.com/jira/browse/JBIDE-2229?page=comments#action_12413189 ]
Max Rydahl Andersen commented on JBIDE-2229:
--------------------------------------------
Environment.getProperties() is definitly not the way to detect the dialect. Look in the
unittests how it is done.
I'm not sure converting all db specific dml is worth it, only do it for the parts that
is relevant/important.
Remeber you can use appliesTo(DialecT) on tests to say if the test is ok for a specific db
or not.
Hibernate Tools - JUnit tests has a lot of errors with Oracle test
connection
-----------------------------------------------------------------------------
Key: JBIDE-2229
URL:
http://jira.jboss.com/jira/browse/JBIDE-2229
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Reporter: Vitali Yemialyanchyk
Assigned To: Vitali Yemialyanchyk
Priority: Minor
Attachments: screenshot-1.jpg, screenshot-2.jpg
1) install Oracle 11g;
2) setup default db;
3) change etc/hibernate.properties:
comment ## HypersonicSQL section,
update ## Oracle section:
hibernate.dialect org.hibernate.dialect.Oracle10gDialect
hibernate.connection.driver_class oracle.jdbc.OracleDriver
hibernate.connection.url jdbc:oracle:thin:@localhost:1521:orcl
hibernate.connection.username SYSTEM
hibernate.connection.password sa
4) add Oracle driver into the progect (on my computer it is
"C:\app\Vitali\product\11.1.0\db_1\jdbc\lib\ojdbc5_g.jar")
5) Run ToolAllTests as JUnit test
screenshot is example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira