??xml version="1.0" encoding="utf-8" standalone="yes"?>HSQL 学习(fn)W记
1.1. 学习(fn)目的
本文档是针对hSQL 数据库方面的基础学习(fn)Qؓ(f)了ə目l成员能够达C用hSQL 数据库的目的?br />1.2. 培训对象
开发h?br />1.3. 常用词及(qing)W号说明
常用词:(x)
hsqlQ一U免费的跨^台的数据库系l?br />E:\hsqldbQ表C是在dos 命o(h)H口下面
1.4. 参考信?br />doc\guide\guide.pdf
2. HSQL
2.1. HSQL q行工具
java -cp ../lib/hsqldb.jar org.hsqldb.util.DatabaseManager
注意hsqldb.jar 文g的文件\?最好能攑ֈclasspath 里面,或者放到当前\径下.
java -cp hsqldb.jar org.hsqldb.util.DatabaseManager
2.2. q行数据?br />启动方式: Server Modes and
In-Process Mode (also called Standalone Mode).
一个test 数据库会(x)包含如下文g:
?test.properties
?test.script
?test.log
?test.data
?test.backup
test.properties 文g包含关于数据库的一般设|?
test.script 文g包含表和其它数据?插入没有~存表的数据.
test.log 文g包含当前数据库的变更.
test.data 文g包含~存表的数据
test.backup 文g是最q持久化状态的表的数据文g的压~备份文?br />所有以上这个文仉是必要的,不能被删?如果数据库没有缓存表,test.data 和test.backup 文g不?x)存?另外,除了以上文gHSQLDB 数据库可以链接到M文本文g,比如cvs 文g.
当操作test 数据库的时? test.log 用于保存数据的变? 当正常SHUTDOWN,q个文g被删除. 否则(不是正常shutdown),q个文g用于再ơ启动的时?重做q些变更.test.lck 文g也用于记录打开的数据库的事? 正常SHUTDOWN,文g也被删除.在一些情况下,test.data.old 文g?x)被创?q删除以前的.
2.3. Server Mode
java -cp ../lib/hsqldb.jar org.hsqldb.Server -database.0 file:mydb -dbname.0 xdb
命o(h)行方?
启动数据,数据库文件mydb,数据库名Uxdb
也可以在 server.properties 文g中定义启动的数据?最?0?br />例如: server.properties:
server.database.0=file:E:/hsqldb/data/mydb
server.dbname.0=xdb
server.database.1=file:E:/hsqldb/data/testdb
server.dbname.1=testdb
server.database.2=mem:adatabase
server.dbname.2=quickdb
启动命o(h): java -cp ../lib/hsqldb.jar org.hsqldb.Server
q行l果如下
java 试E序:
package test;
import junit.framework.TestCase;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
public class TestConnect extends TestCase {
Connection connection;
protected void setUp()
{
try {
Class.forName("org.hsqldb.jdbcDriver" );
connection = DriverManager.getConnection("jdbc:hsqldb:hsql://localhost/xdb","sa","");
} catch (Exception e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
public void testselect()
{
Statement stmt=null;
ResultSet rs=null;
try {
stmt = connection.createStatement();
String sql ="select * from test";
rs=stmt.executeQuery( sql);
while(rs.next() )
{
System.out.println("id="+rs.getString("id"));
System.out.println("name="+rs.getString("name"));
}
} catch (SQLException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
finally
{
try {
rs.close() ;
stmt.close();
} catch (SQLException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}
protected void tearDown()
{
try {
connection.close();
} catch (Exception e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}
以上在eclipse 中测试通过.
2.4. In-Process (Standalone) Mode
不需要启动server
connection = DriverManager.getConnection("jdbc:hsqldb:file:E:/hsqldb/data/mydb","sa","");
q样可以连接数据库?br />只能在一个jvm 中用,不能在多个jvm 中用?br />q种模式是在相同的jvm 下作Z的应用程序的一部分Q运行数据库引擎。对大多数应用程序,q种模式q行?x)相当快Q作为数据,不需要{换和|络传输?br />
主要的缺点就是不可能从外面的应用E序讉K到默认数据库Q因此当你的应用q行时候,你不能通过别的工具查数据库内容。在1.8.0 版本?你可以在相同jvm 中的U程中运行数据库初始化,q提供外面访问你的进E内数据库?br /> 推荐在开发应用中使用q种方式?br />q接Ԍ(x)
Windows: DriverManager.getConnection("jdbc:hsqldb:file:E:/hsqldb/data/mydb","sa","");
Unix: DriverManager.getConnection("jdbc:hsqldb:file:/opt/db/testdb","sa","");
2.5. Memory-Only Databases
当随卌问内存,数据库不固定Ӟ可以采用内存的方式运行数据库Q由于没有数据写到硬盘上Q这U方式用在应用数据和applets 和特D应用的内部q程中用,URLQ?br />
Connection c = DriverManager.getConnection("jdbc:hsqldb:mem:aname", "sa", "");
2.6. Using Multiple Databases in One JVM
2.7. Different Types of Tables
HSQLDB 支持 TEMP 表和三种cd的持久表QMEMORY ? CACHED 表,TEXT表)
当?CREATE TABLE 命o(h)ӞMemory 表时默认cdQ它们的数据整体保存在内存当中,但是M改变它们的结构或者内容,它们?x)被写?lt;dbname>.script 文g中。这个脚本文件在数据库下一ơ打开的时候被对出Q内存表重新被创建内容,根temp 表不同,内存表时持久化的?br />
CACHED 表通过CREATE CACHED TABLE 命o(h)建立. 只有部分的它们的数据或者烦引被保存在内存中Q允许大表占用几癑օ的内存空间。例外一个优点,在数据库引擎中,启动大量数据的缓存表需要花费少量的旉Q缺Ҏ(gu)减慢了运行和使用Hsqldb 的速度。表相对的时候,不要使用cache 表,在小表中使用内存数据库?br />
从版?1.7.0 以后Q支持text 表,使用 CSV (Comma Separated Value) 或者其它分隔符文本文g作ؓ(f)它们的数据源。你可以Ҏ(gu)指定一个存在的CSV 文gQ例如从其它的数据或者程序中导出文gQ作为TXT 表的数据源?同时,你可以指定一个空文gQ通过数据库引擎填充数据。TEXT 表将比cache 表更加效率高。Text 表可以指向不同的数据文g?br />
* memory-only databases 数据库只支持memory 表和cache 表,不支持text 表?br />2.8. U束和烦?br />HSQLDB 支持 PRIMARY KEY, NOT NULL, UNIQUE, CHECK and FOREIGN KEY U束.
3. sql 命o(h)
3.1. sql 支持
select top 1 * from test;
select limit 0 2 * from test;
DROP TABLE test IF EXISTS;
3.2. Constraints and Indexes
dU束QPRIMARY KEY
唯一U束Q?br />唯一索引Q?br />外健Q?br />CREATE TABLE child(c1 INTEGER, c2 VARCHAR, FOREIGN KEY (c1, c2) REFERENCES parent(p1, p2));
3.3. 索引和查询速度
索引提高查询速度Q比提高排序速度?br />d和唯一所列自动创建烦引,否则需要自己创建CREATE INDEX command?br />索引Q?唯一索引和非唯一索引
多列的烦引,如果只是使用后面的,不用第一个,不?x)条查询速度?br />
(TB is a very large table with only a few rows where TB.COL3 = 4)
SELECT * FROM TA JOIN TB ON TA.COL1 = TB.COL2 AND TB.COL3 = 4;
SELECT * FROM TB JOIN TA ON TA.COL1 = TB.COL2 AND TB.COL3 = 4;(faster)
原因?TB.COL3 可以被快速的估计,如果TB 表放到前?index on TB.COL3):
一般规则是把羃?yu)条件的列的表放在前?br />
3.4. 使用where q是join
使用 WHERE 条g链接表可能会(x)降低q行速度.
下面的例子将?x)比较?即使用了烦?
SELECT ... FROM TA, TB, TC WHERE TC.COL3 = TA.COL1 AND TC.COL3=TB.COL2 AND TC.COL4 = 1
q个查询隐含TA.COL1 = TB.COL2 ,但是没有直接讑֮q个条g.如果 TA ?TB 每个表都包含100 条记?10000 l合和 TC 兌,用于TCq个列的条g,管有烦引在q个列上.使用JOIN 关键? 在组合TC 之前,TA.COL1 = TB.COL2 条g直接q羃?yu)组?TA ?TB 的行? 在运行大数据量的表的l果?会(x)很快:
SELECT ... FROM TA JOIN TB ON TA.COL1 = TB.COL2 JOIN TC ON TB.COL2 = TC.COL3 WHERE TC.COL4 = 1
q个查询可以提高一大步,如果改变表的序, 所?TC.COL1 = 1 最先?q样更小的集合将l合在一?
SELECT ... FROM TC JOIN TB ON TC.COL3 = TB.COL2 JOIN TA ON TC.COL3 = TA.COL1 WHERE TC.COL4 = 1
以上例子,数据引擎自动应用于TC.COL4 = 1 l合的集合于其它表兌. Indexes TC.COL4, TB.COL2 TA.COL1 都将使用索引,提高查询速度.
3.5. Subqueries and Joins
使用join 和调整表的顺序提高效?
例如:, W二个查询的速度更快一?TA.COL1 和TB.COL3都有索引):
Example 2.2. Query comparison
SELECT ... FROM TA WHERE TA.COL1 = (SELECT MAX(TB.COL2) FROM TB WHERE TB.COL3 = 4)
SELECT ... FROM (SELECT MAX(TB.COL2) C1 FROM TB WHERE TB.COL3 = 4) T2 JOIN TA ON TA.COL1 = T2.C1
W二个查询将 MAX(TB.COL2) 与一个单记录表相兌. q用TA.COL1索引,q将变得非常? W一个查询是?TA 表中的每一条记录不断地与MAX(TB.COL2)匚w.
3.6. 数据cd
TINYINT, SMALLINT, INTEGER, BIGINT, NUMERIC and DECIMAL (without a decimal point) are supported integral types and map to byte, short, int, long and BigDecimal in Java.
Integral Types:
TINYINT, SMALLINT, INTEGER, BIGINT, NUMERIC and DECIMAL
Other Numeric Types:
REAL, FLOAT or DOUBLE
Bit and Boolean Types:
BOOLEAN: UNDEFINED,TRUE,FALSE
NULL values are treated as undefined.
Storage and Handling of Java Objects
Sequences and Identity
Identity Auto-Increment Columns:
The next IDENTITY value to be used can be set with the
ALTER TABLE ALTER COLUMN <column name> RESTART WITH <new value>;
Sequences:
SELECT NEXT VALUE FOR mysequence, col1, col2 FROM mytable WHERE ...
3.7. 事务问题:
SET PROPERTY "sql.tx_no_multi_rewrite" TRUE
4. Connections
通用驱动jdbc:hsqldb: 下列协议标识(mem: file: res: hsql: http: hsqls: https:)
Table 4.1. Hsqldb URL Components
Driver and Protocol Host and Port Database
jdbc:hsqldb:mem:
not available accounts
jdbc:hsqldb:mem:.
jdbc:hsqldb:file:
not available mydb
/opt/db/accounts
C:/data/mydb
数据库\?
jdbc:hsqldb:res:
not available /adirectory/dbname
jars files are accessed in Java programs. The /adirectory above stands for a directory in one of the jars.
jdbc:hsqldb:hsql:
jdbc:hsqldb:hsqls:
jdbc:hsqldb:http:
jdbc:hsqldb:https:
//localhost
//192.0.0.10:9500
//dbserver.somedomain.com
/an_alias
/enrollments
/quickdb
别名在server.properties or webserver.properties文g中指?br /> database.0=file:/opt/db/accounts
dbname.0=an_alias
database.1=file:/opt/db/mydb
dbname.1=enrollments
database.2=mem:adatabase
dbname.2=quickdb
In the example below, the database files lists.* in the /home/dbmaster/ directory are associated with the empty alias:
database.3=/home/dbmaster/lists
dbname.3=
4.1. Connection properties
Connection properties are specified either by establishing the connection via the:
DriverManager.getConnection (String url, Properties info);
method call, or the property can be appended to the full Connection URL.
Table 4.2. Connection Properties
get_column_name true column name in ResultSet
This property is used for compatibility with other JDBC driver implementations. When true (the default), ResultSet.getColumnName(int c) returns the underlying column name
When false, the above method returns the same value as ResultSet.getColumnLabel(int column) Example below:
jdbc:hsqldb:hsql://localhost/enrollments;get_column_name=false
When a ResultSet is used inside a user-defined stored procedure, the default, true, is always used for this property.
ifexists false connect only if database already exists
Has an effect only with mem: and file: database. When true, will not create a new database if one does not already exist for the URL.
When false (the default), a new mem: or file: database will be created if it does not exist.
Setting the property to true is useful when troubleshooting as no database is created if the URL is malformed. Example below:
jdbc:hsqldb:file:enrollments;ifexists=true
shutdown false shut down the database when the last connection is closed
This mimics the behaviour of 1.7.1 and older versions. When the last connection to a database is closed, the database is automatically shut down. The property takes effect only when the first connection is made to the database. This means the connection that opens the database. It has no effect if used with subsequent, simultaneous connections.
This command has two uses. One is for test suites, where connections to the database are made from one JVM context, immediately followed by another context. The other use is for applications where it is not easy to configure the environment to shutdown the database. Examples reported by users include web application servers, where the closing of the last connection conisides with the web app being shut down.
4.2. Properties Files
大小写敏?(e.g. server.silent=FALSE will have no effect, but server.silent=false will work).
属性文件和讑֮存储如下 :
Table 4.3. Hsqldb Server Properties Files
File Name Location Function
server.properties the directory where the command to run the Server class is issued settings for running HSQLDB as a database server communicating with the HSQL protocol
webserver.properties the directory where the command to run the WebServer class is issued settings for running HSQLDB as a database server communicating with the HTTP protocol
<dbname>.properties the directory where all the files for a database are located settings for each particular database
Properties files for running the servers are not created automatically. You should create your own files that contain server.property=value pairs for each property.
4.2.1. Server and Web Server Properties
server.properties and webserver.properties 文g支持如下讑֮:
Table 4.4. Property File Properties
Value Default Description
server.database.0 test the path and file name of the first database file to use
server.dbname.0 "" lowercase server alias for the first database file
server.urlid.0 NONE SqlTool urlid used by UNIX init script. (This property is not used if your are running Server/Webserver on a platform other than UNIX, or of you are not using our UNIX init script).
server.silent true no extensive messages displayed on console
server.trace false JDBC trace messages displayed on console
In 1.8.0, 每个服务器支持同时启?0个不同的数据? The server.database.0 property defines the filename / path whereas the server.dbname.0 defines the lowercase alias used by clients to connect to that database. The digit 0 is incremented for the second database and so on. Values for the server.database.{0-9} property can use the mem:, file: or res: prefixes and properties as discussed above under CONNECTIONS. For example,
database.0=mem:temp;sql.enforce_strict_size=true;
Values specific to server.properties are:
Table 4.5. Server Property File Properties
Value Default Description
server.port 9001 TCP/IP port used for talking to clients. All databases are served on the same port.
server.no_system_exit true no System.exit() call when the database is closed
Values specific to webserver.properties are:
Table 4.6. WebServer Property File Properties
Value Default Description
server.port 80 TCP/IP port used for talking to clients
server.default_page index.html the default web page for server
server.root ./ the location of served pages
.<extension> ? multiple entries such as .html=text/html define the mime types of the static files served by the web server. See the source for WebServer.java for a list.
All the above values can be specified on the command line to start the server by omitting the server. prefix.
5. SqlTool
Mem 数据?
E:\hsqldb>java -jar ./lib/hsqldb.jar mem
Hsql Server:
(前提是xdb server 已经启动):
(java -cp ../lib/hsqldb.jar org.hsqldb.Server -database.0 file:mydb -dbname.0 xdb)
java -jar ./hsqldb.jar xdb
]]>
DbUnit?/strong>
Z赖于其他外部pȝQ如数据库或其他接口Q的代码~写单元试是一件很困难的工作。在q种情况下,有效的单元必隔L试对象和外部依赖Q以便管理测试对象的状态和行ؓ(f)?/p>
使用mock object对象Q是隔离外部依赖的一个有效方法。如果我们的试对象是依赖于DAO的代码,mock object技术很方便。但如果试对象变成了DAO本nQ又如何q行单元试呢?
开源的DbUnit目Qؓ(f)以上的问题提供了一个相当优雅的解决Ҏ(gu)。用DbUnitQ开发h员可以控制测试数据库的状态。进行一个DAO单元试之前QDbUnit为数据库准备好初始化数据Q而在试l束ӞDbUnit?x)把数据库状态恢复到试前的状态?/p>
下面的例子用DbUnit为iBATIS SqlMap的DAO~写单元试?/p>
准备试数据
首先Q要为单元测试准备数据。用DbUnitQ我们可以用XML文g来准备测试数据集。下面的XML文gUCؓ(f)目标数据库的Seed FileQ代表目标数据库的表名和数据Q它为测试准备了两个Employee的数据。employee对应数据库的表名Qemployee_uid、start_date、first_name和last_name都是表employee的列名?/span>
<?xml version="1.0" encoding="GB2312"?>
<dataset>
<employee employee_uid="0001"
start_date="2001-01-01"
first_name="liutao"
last_name="liutao" />
<employee employee_uid="0002"
start_date="2001-04-01"
first_name="wangchuang"
last_name="wangchuang" />
</dataset>
~省情况下,DbUnit在单元测试开始之前删除Seed File中所有表的数据,然后导入Seed File的测试数据。在Seed File中不存在的表QDbUnit则不处理?br />Seed File可以手工~写Q也可以用程序导出现有的数据库数据ƈ生成?br />
SqlMap代码
我们要测试的SqlMap映射文g如下所C:(x)
<select id="queryEmployeeById" parameterClass="java.lang.String"
resultClass="domain.Employee">
select employee_uid as userId,
start_date as startDate,
first_name as firstName,
last_name as lastName
from EMPLOYEE where employee_uid=#value#
</select>
<delete id="removeEmployeeById" parameterClass="java.lang.String">
delete from EMPLOYEE where employee_uid=#value#
</delete>
<update id="updateEmpoyee" parameterClass="domain.Employee">
update EMPLOYEE
set start_date=#startDate#,
first_name=#firstName#,
last_name=#lastName#
where employee_uid=#userId#
</update>
<insert id="insertEmployee" parameterClass="domain.Employee">
insert into employee (employee_uid,
start_date, first_name, last_name)
values (#userId#, #startDate#, #firstName#, #lastName#)
</insert>
~写DbUnit TestCase
Z方便试Q首先ؓ(f)SqlMap的单元测试编写一个抽象的试基类Q代码如下?/span>
public abstract class BaseSqlMapTest extends DatabaseTestCase {
protected static SqlMapClient sqlMap;
protected IDatabaseConnection getConnection() throws Exception {
return new DatabaseConnection(getJdbcConnection());
}
protected void setUp() throws Exception {
super.setUp();
init();
}
protected void tearDown() throws Exception {
super.tearDown();
getConnection().close();
if (sqlMap != null) {
DataSource ds = sqlMap.getDataSource();
Connection conn = ds.getConnection();
conn.close();
}
}
protected void init() throws Exception {
initSqlMap("sqlmap/SqlMapConfig.xml", null);
}
protected SqlMapClient getSqlMapClient() {
return sqlMap;
}
protected void initSqlMap(String configFile, Properties props)
throws Exception {
Reader reader = Resources.getResourceAsReader(configFile);
sqlMap = SqlMapClientBuilder.buildSqlMapClient(reader, props);
reader.close();
}
protected void initScript(String script) throws Exception {
DataSource ds = sqlMap.getDataSource();
Connection conn = ds.getConnection();
Reader reader = Resources.getResourceAsReader(script);
ScriptRunner runner = new ScriptRunner();
runner.setStopOnError(false);
runner.setLogWriter(null);
runner.setErrorLogWriter(null);
runner.runScript(conn, reader);
conn.commit();
conn.close();
reader.close();
}
private Connection getJdbcConnection() throws Exception {
Properties props = new Properties();
props.load(Resources.getResourceAsStream("sqlmap/SqlMapConfig.properties"));
Class driver = Class.forName(props.getProperty("driver"));
Connection conn = DriverManager.getConnection(props.getProperty("url"),
props.getProperty("username"), props.getProperty("password"));
return conn;
}
}
然后为每个SqlMap映射文g~写一个测试用例,extends上面的抽象类。如~写Employ.xml的测试用例如下,它覆盖了DbUnit的DatabaseTestCasecȝgetDataSetҎ(gu)?br />
public class EmployeeDaoTest extends BaseSqlMapTest {
protected IDataSet getDataSet() throws Exception {
Reader reader = Resources.getResourceAsReader("config/employee_seed.xml");
return new FlatXmlDataSet(reader);
}
public void testQueryEmpoyeeById() throws Exception {
String id = "0001";
Employee emp = (Employee)sqlMap.queryForObject("queryEmployeeById", id);
assertNotNull(emp);
assertEquals("0001", emp.getUserId());
assertEquals("liutao", emp.getFirstName());
}
public void testRemoveEmployeeById() throws Exception {
String id = "0001";
int num = sqlMap.delete("removeEmployeeById", id);
assertEquals(1, num);
// 注意q里, 认删除不能使用SqlMap的查? 很奇怪!
ITable table = getConnection().createQueryTable("removed",
"select * from employee where employee_uid='0001'");
assertEquals(0, table.getRowCount());
}
public void testUpdateEmployee() throws Exception {
String id = "0002";
Employee emp = (Employee)sqlMap.queryForObject("queryEmployeeById", id);
emp.setLastName("wch");
sqlMap.update("updateEmpoyee", emp);
Employee emp1 = (Employee)sqlMap.queryForObject("queryEmployeeById", id);
assertEquals("wch", emp1.getLastName());
}
public void testInsertEmployee() throws Exception {
Employee emp = new Employee();
emp.setUserId("0005");
emp.setStartDate("2003-09-09");
emp.setFirstName("macy");
emp.setLastName("macy");
sqlMap.insert("insertEmployee", emp);
Employee emp1 = (Employee)sqlMap.queryForObject("queryEmployeeById", "0005");
assertEquals(emp.getFirstName(), emp1.getFirstName());
assertEquals(emp.getStartDate(), emp1.getStartDate());
}
}
以上例子中的l色代码部分使用ITable接口来查询已删除的数据。因Z用SqlMapClient.queryForObjectҎ(gu)查询Q已删除的数据还存在Q真奇怪(有时间再研究Q?br />
DbUnit的断a
我们可以使用DbUnit的AssertioncȝҎ(gu)来比较数据是否相同?br />
public class Assertion {
public static void assertEquals(ITable expected, ITable actual)
public static void assertEquals(IDataSet expected, IDataSet actual)
}
DatabaseTestCase的getSetUpOperation和getTearDownOperationҎ(gu)
~省情况下,DbUnit执行每个试前,都会(x)执行CLEAN_INSERT操作Q删除Seed File中所有表的数据,q插入文件的试数据。你可以通过覆盖getSetUpOperation和getTearDownOperationҎ(gu)改变setUp和tearDown的行为?br />
protected DatabaseOperation getSetUpOperation() throws Exception {
return DatabaseOperation.REFRESH;
}
protected DatabaseOperation
getTearDownOperation()
throws Exception {
return DatabaseOperation.NONE;
}
REFRESH操作执行试前ƈ不执行CLEAN操作Q只是导入文件中的数据,如果目标数据库数据已存在QDbUnit使用文g的数据来更新数据库?/span>
使用Ant
上面的方法通过extends DbUnit的DatabaseTestCase来控制数据库的状态。?/span>
使用DbUnit的Ant TaskQ完全可以通过Ant脚本的方式来实现?/span>
<taskdef name="dbunit" classname="org.dbunit.ant.DbUnitTask"/>
<!-- 执行set up 操作 -->
<dbunit driver="org.hsqldb.jdbcDriver"
url="jdbc:hsqldb:hsql://localhost/xdb"
userid="sa" password="">
<operation type="INSERT" src="employee_seed.xml"/>
</dbunit>
<!-- run all tests in the source tree -->
<junit printsummary="yes" haltonfailure="yes">
<formatter type="xml"/>
<batchtest fork="yes" todir="${reports.tests}">
<fileset dir="${src.tests}">
<include name="**/*Test*.java"/>
</fileset>
</batchtest>
</junit>
<!-- 执行tear down 操作 -->
<dbunit driver="org.hsqldb.jdbcDriver"
url="jdbc:hsqldb:hsql://localhost/xdb"
userid="sa" password="">
<operation type="DELETE" src="employee_seed.xml"/>
</dbunit>
以上的Ant脚本把junit task攑֜DbUnit的Task中间Q可以达到控制数据库状态的目标?br />
由此可知QDbUnit可以灉|控制目标数据库的试状态,从而ɾ~写SqlMap单元试变得更加L?br />
本文抄袭了资源列表的“Effective Unit Test with DbUnit”,但重新编写了代码CZ?br />
|上资源
1?a >DbUnit Framework
2?a >Effective Unit Testing with DbUnit
3?a >Control your test-environement with DbUnit and Anthill