Menu
▾
▴
dbunit-commit
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(7) |
Aug
(37) |
Sep
|
Oct
|
Nov
(1) |
Dec
(22) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(8) |
Feb
(68) |
Mar
(72) |
Apr
(149) |
May
(32) |
Jun
(46) |
Jul
(26) |
Aug
(59) |
Sep
(25) |
Oct
(18) |
Nov
(4) |
Dec
(3) |
| 2004 |
Jan
(90) |
Feb
(19) |
Mar
(38) |
Apr
(41) |
May
(44) |
Jun
(2) |
Jul
(10) |
Aug
|
Sep
(14) |
Oct
|
Nov
(1) |
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(15) |
Jun
(1) |
Jul
|
Aug
(9) |
Sep
|
Oct
(17) |
Nov
|
Dec
|
| 2006 |
Jan
(1) |
Feb
(16) |
Mar
|
Apr
(1) |
May
(48) |
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(29) |
| 2007 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
(23) |
Mar
(31) |
Apr
|
May
(26) |
Jun
(6) |
Jul
(1) |
Aug
|
Sep
(7) |
Oct
(1) |
Nov
(8) |
Dec
(8) |
| 2009 |
Jan
(5) |
Feb
(9) |
Mar
(1) |
Apr
|
May
(23) |
Jun
(3) |
Jul
|
Aug
(1) |
Sep
(9) |
Oct
(28) |
Nov
(18) |
Dec
(8) |
| 2010 |
Jan
(19) |
Feb
(24) |
Mar
(3) |
Apr
|
May
(5) |
Jun
(4) |
Jul
|
Aug
(1) |
Sep
(11) |
Oct
|
Nov
(2) |
Dec
(1) |
| 2011 |
Jan
|
Feb
(7) |
Mar
|
Apr
(6) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(32) |
Oct
(6) |
Nov
|
Dec
|
|
From: <mla...@us...> - 2004-01-18 18:22:45
|
Update of /cvsroot/dbunit/dbunit/src/java/org/dbunit/ant
In directory sc8-pr-cvs1:/tmp/cvs-serv23989/src/java/org/dbunit/ant
Modified Files:
DbUnitTask.java
Log Message:
Added warning when encounter unrecognized data type. This warning can be disabled by a DatabaseConfig feature.
Index: DbUnitTask.java
===================================================================
RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/ant/DbUnitTask.java,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** DbUnitTask.java 16 Sep 2003 05:08:30 -0000 1.9
--- DbUnitTask.java 18 Jan 2004 18:22:42 -0000 1.10
***************
*** 95,102 ****
/**
! * Flag for using botched statements.
*/
private boolean supportBatchStatement = false;
private String escapePattern = null;
--- 95,107 ----
/**
! * Flag for using batched statements.
*/
private boolean supportBatchStatement = false;
+ /**
+ * Flag for datatype warning.
+ */
+ private boolean datatypeWarning = true;
+
private String escapePattern = null;
***************
*** 161,164 ****
--- 166,174 ----
}
+ public void setDatatypeWarning(boolean datatypeWarning)
+ {
+ this.datatypeWarning = datatypeWarning;
+ }
+
public void setDatatypeFactory(String datatypeFactory)
{
***************
*** 354,357 ****
--- 364,368 ----
config.setFeature(DatabaseConfig.FEATURE_BATCHED_STATEMENTS, supportBatchStatement);
config.setFeature(DatabaseConfig.FEATURE_QUALIFIED_TABLE_NAMES, useQualifiedTableNames);
+ config.setFeature(DatabaseConfig.FEATURE_DATATYPE_WARNING, datatypeWarning);
config.setProperty(DatabaseConfig.PROPERTY_ESCAPE_PATTERN, escapePattern);
config.setProperty(DatabaseConfig.PROPERTY_RESULTSET_TABLE_FACTORY,
|
|
From: <mla...@us...> - 2004-01-18 16:39:27
|
Update of /cvsroot/dbunit/dbunit/src/java/org/dbunit/dataset/xml In directory sc8-pr-cvs1:/tmp/cvs-serv29943/src/java/org/dbunit/dataset/xml Modified Files: FlatXmlDataSet.java XmlDataSet.java Log Message: Javadoc updates Index: FlatXmlDataSet.java =================================================================== RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/dataset/xml/FlatXmlDataSet.java,v retrieving revision 1.23 retrieving revision 1.24 diff -C2 -d -r1.23 -r1.24 *** FlatXmlDataSet.java 9 Aug 2003 11:23:22 -0000 1.23 --- FlatXmlDataSet.java 18 Jan 2004 16:39:24 -0000 1.24 *************** *** 39,42 **** --- 39,69 ---- /** + * Reads and writes flat XML dataset document. Each XML element corresponds to a table row. + * Each XML element name corresponds to a table name. The XML attributes + * correspond to table columns. + * <p> + * Flat XML dataset document sample: + * <p> + * <pre> + * <!DOCTYPE dataset SYSTEM "my-dataset.dtd"> + * <dataset> + * <TEST_TABLE COL0="row 0 col 0" + * COL1="row 0 col 1" + * COL2="row 0 col 2"/> + * <TEST_TABLE COL1="row 1 col 1"/> + * <SECOND_TABLE COL0="row 0 col 0" + * COL1="row 0 col 1" /> + * <EMPTY_TABLE/> + * </dataset></pre> + * <p> + * To specify null values, omit corresponding attribute. + * In the above example, missing COL0 and COL2 attributes of TEST_TABLE second row represents null values. + * <p> + * Table metadata is deduced from the first row of each table. <b>Beware that DbUnit may think + * a table miss some columns if the first row of that table has one or more null values.</b> + * Because of that, this is highly recommended to use DTD. DbUnit will use the + * columns declared in the DTD as table metadata. DbUnit only support external system URI. + * The URI can be absolute or relative. + * * @author Manuel Laflamme * @version $Revision$ Index: XmlDataSet.java =================================================================== RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/dataset/xml/XmlDataSet.java,v retrieving revision 1.17 retrieving revision 1.18 diff -C2 -d -r1.17 -r1.18 *** XmlDataSet.java 19 Jun 2003 03:17:16 -0000 1.17 --- XmlDataSet.java 18 Jan 2004 16:39:24 -0000 1.18 *************** *** 37,43 **** /** ! * Provides persistence support to read from and write to the dbunit xml format. ! * This format is specified by the dataset.dtd file. * * @author Manuel Laflamme * @version $Revision$ --- 37,55 ---- /** ! * Reads and writes original XML dataset document. This format ! * is very verbiose and must conform to the following DTD: ! * <pre> * + * <?xml version="1.0" encoding="UTF-8"?> + * <!ELEMENT dataset (table+)> + * <!ELEMENT table (column*, row*)> + * <!ATTLIST table + * name CDATA #REQUIRED + * > + * <!ELEMENT column (#PCDATA)> + * <!ELEMENT row (value | null | none)*> + * <!ELEMENT value (#PCDATA)> + * <!ELEMENT null EMPTY> + *</pre> * @author Manuel Laflamme * @version $Revision$ |
Update of /cvsroot/dbunit/dbunit/src/java/org/dbunit/operation
In directory sc8-pr-cvs1:/tmp/cvs-serv29943/src/java/org/dbunit/operation
Modified Files:
AbstractBatchOperation.java DatabaseOperation.java
DeleteAllOperation.java RefreshOperation.java
Added Files:
AbstractOperation.java
Log Message:
Javadoc updates
--- NEW FILE: AbstractOperation.java ---
/*
*
* The DbUnit Database Testing Framework
* Copyright (C)2002, Manuel Laflamme
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Lesser General Public
* License as published by the Free Software Foundation; either
* version 2.1 of the License, or (at your option) any later version.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
*
*/
package org.dbunit.operation;
import org.dbunit.database.IDatabaseConnection;
import org.dbunit.database.DatabaseConfig;
import org.dbunit.dataset.DataSetUtils;
/**
* @author Manuel Laflamme
* @since Jan 17, 2004
* @version $Revision: 1.1 $
*/
public abstract class AbstractOperation extends DatabaseOperation
{
protected String getQualifiedName(String prefix, String name, IDatabaseConnection connection)
{
String escapePattern = (String)connection.getConfig().getProperty(
DatabaseConfig.PROPERTY_ESCAPE_PATTERN);
return DataSetUtils.getQualifiedName(prefix, name, escapePattern);
}
}
Index: AbstractBatchOperation.java
===================================================================
RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/operation/AbstractBatchOperation.java,v
retrieving revision 1.20
retrieving revision 1.21
diff -C2 -d -r1.20 -r1.21
*** AbstractBatchOperation.java 9 Jan 2004 21:58:31 -0000 1.20
--- AbstractBatchOperation.java 18 Jan 2004 16:39:24 -0000 1.21
***************
*** 41,45 ****
* @version $Revision$
*/
! public abstract class AbstractBatchOperation extends DatabaseOperation
{
private static final BigInteger EMPTY_IGNORE_MAPPING = new BigInteger("0");
--- 41,45 ----
* @version $Revision$
*/
! public abstract class AbstractBatchOperation extends AbstractOperation
{
private static final BigInteger EMPTY_IGNORE_MAPPING = new BigInteger("0");
Index: DatabaseOperation.java
===================================================================
RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/operation/DatabaseOperation.java,v
retrieving revision 1.12
retrieving revision 1.13
diff -C2 -d -r1.12 -r1.13
*** DatabaseOperation.java 9 Aug 2003 11:23:30 -0000 1.12
--- DatabaseOperation.java 18 Jan 2004 16:39:24 -0000 1.13
***************
*** 23,34 ****
package org.dbunit.operation;
- import java.sql.SQLException;
-
import org.dbunit.DatabaseUnitException;
- import org.dbunit.database.DatabaseConfig;
import org.dbunit.database.IDatabaseConnection;
- import org.dbunit.dataset.DataSetUtils;
import org.dbunit.dataset.IDataSet;
/**
* Defines the interface contract for operations performed on the database.
--- 23,32 ----
package org.dbunit.operation;
import org.dbunit.DatabaseUnitException;
import org.dbunit.database.IDatabaseConnection;
import org.dbunit.dataset.IDataSet;
+ import java.sql.SQLException;
+
/**
* Defines the interface contract for operations performed on the database.
***************
*** 59,70 ****
IDataSet dataSet) throws DatabaseUnitException, SQLException;
- public static String getQualifiedName(String prefix, String name, IDatabaseConnection connection)
- {
- String escapePattern = (String)connection.getConfig().getProperty(
- DatabaseConfig.PROPERTY_ESCAPE_PATTERN);
-
- return DataSetUtils.getQualifiedName(prefix, name, escapePattern);
- }
-
private static class DummyOperation extends DatabaseOperation
{
--- 57,60 ----
Index: DeleteAllOperation.java
===================================================================
RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/operation/DeleteAllOperation.java,v
retrieving revision 1.16
retrieving revision 1.17
diff -C2 -d -r1.16 -r1.17
*** DeleteAllOperation.java 1 Aug 2003 02:29:11 -0000 1.16
--- DeleteAllOperation.java 18 Jan 2004 16:39:24 -0000 1.17
***************
*** 46,50 ****
* @see TruncateTableOperation
*/
! public class DeleteAllOperation extends DatabaseOperation
{
DeleteAllOperation()
--- 46,50 ----
* @see TruncateTableOperation
*/
! public class DeleteAllOperation extends AbstractOperation
{
DeleteAllOperation()
Index: RefreshOperation.java
===================================================================
RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/operation/RefreshOperation.java,v
retrieving revision 1.29
retrieving revision 1.30
diff -C2 -d -r1.29 -r1.30
*** RefreshOperation.java 9 Jan 2004 21:58:31 -0000 1.29
--- RefreshOperation.java 18 Jan 2004 16:39:24 -0000 1.30
***************
*** 51,55 ****
* @version $Revision$
*/
! public class RefreshOperation extends DatabaseOperation
{
private final InsertOperation _insertOperation;
--- 51,55 ----
* @version $Revision$
*/
! public class RefreshOperation extends AbstractOperation
{
private final InsertOperation _insertOperation;
|
|
From: <mla...@us...> - 2004-01-18 16:39:27
|
Update of /cvsroot/dbunit/dbunit/src/java/org/dbunit/operation/mssqlserver
In directory sc8-pr-cvs1:/tmp/cvs-serv29943/src/java/org/dbunit/operation/mssqlserver
Modified Files:
InsertIdentityOperation.java
Log Message:
Javadoc updates
Index: InsertIdentityOperation.java
===================================================================
RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/operation/mssqlserver/InsertIdentityOperation.java,v
retrieving revision 1.19
retrieving revision 1.20
diff -C2 -d -r1.19 -r1.20
*** InsertIdentityOperation.java 26 Nov 2003 17:00:24 -0000 1.19
--- InsertIdentityOperation.java 18 Jan 2004 16:39:24 -0000 1.20
***************
*** 37,40 ****
--- 37,41 ----
import org.dbunit.operation.DatabaseOperation;
import org.dbunit.operation.ExclusiveTransactionException;
+ import org.dbunit.operation.AbstractOperation;
/**
***************
*** 56,60 ****
* @version $Revision$
*/
! public class InsertIdentityOperation extends DatabaseOperation
{
public static final DatabaseOperation INSERT =
--- 57,61 ----
* @version $Revision$
*/
! public class InsertIdentityOperation extends AbstractOperation
{
public static final DatabaseOperation INSERT =
|
|
From: <mla...@us...> - 2004-01-18 16:39:27
|
Update of /cvsroot/dbunit/dbunit/src/java/org/dbunit/dataset/stream
In directory sc8-pr-cvs1:/tmp/cvs-serv29943/src/java/org/dbunit/dataset/stream
Modified Files:
StreamingDataSet.java
Log Message:
Javadoc updates
Index: StreamingDataSet.java
===================================================================
RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/dataset/stream/StreamingDataSet.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** StreamingDataSet.java 10 Oct 2003 21:12:37 -0000 1.1
--- StreamingDataSet.java 18 Jan 2004 16:39:23 -0000 1.2
***************
*** 29,32 ****
--- 29,34 ----
/**
+ * Dataset that consumes producer asyncronously.
+ *
* @author Manuel Laflamme
* @since Apr 18, 2003
***************
*** 68,71 ****
--- 70,77 ----
// IDataSet interface
+ /**
+ * Not supported.
+ * @throws UnsupportedOperationException
+ */
public String[] getTableNames() throws DataSetException
{
***************
*** 73,76 ****
--- 79,86 ----
}
+ /**
+ * Not supported.
+ * @throws UnsupportedOperationException
+ */
public ITableMetaData getTableMetaData(String tableName) throws DataSetException
{
***************
*** 78,81 ****
--- 88,95 ----
}
+ /**
+ * Not supported.
+ * @throws UnsupportedOperationException
+ */
public ITable getTable(String tableName) throws DataSetException
{
|
|
From: <mla...@us...> - 2004-01-18 16:39:26
|
Update of /cvsroot/dbunit/dbunit/src/java/org/dbunit/dataset/filter In directory sc8-pr-cvs1:/tmp/cvs-serv29943/src/java/org/dbunit/dataset/filter Modified Files: ExcludeTableFilter.java IncludeTableFilter.java Log Message: Javadoc updates Index: ExcludeTableFilter.java =================================================================== RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/dataset/filter/ExcludeTableFilter.java,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** ExcludeTableFilter.java 9 Aug 2003 11:23:15 -0000 1.4 --- ExcludeTableFilter.java 18 Jan 2004 16:39:23 -0000 1.5 *************** *** 24,28 **** /** * This filter hides specified tables from the filtered dataset. This ! * implementation do not modify the original table sequence from the filtered * dataset and support duplicate table names. * --- 24,28 ---- /** * This filter hides specified tables from the filtered dataset. This ! * implementation do not modify the original table order from the filtered * dataset and support duplicate table names. * Index: IncludeTableFilter.java =================================================================== RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/dataset/filter/IncludeTableFilter.java,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** IncludeTableFilter.java 20 Mar 2003 03:05:13 -0000 1.4 --- IncludeTableFilter.java 18 Jan 2004 16:39:23 -0000 1.5 *************** *** 29,34 **** * implementation do not modify the original table sequence from the filtered * dataset and support duplicate table names. - * <p> - * The pattern matching code is taken from the Apache Ant project. * * @author Manuel Laflamme --- 29,32 ---- |
|
From: <mla...@us...> - 2004-01-18 16:39:26
|
Update of /cvsroot/dbunit/dbunit/src/java/org/dbunit/dataset
In directory sc8-pr-cvs1:/tmp/cvs-serv29943/src/java/org/dbunit/dataset
Modified Files:
CachedDataSet.java CompositeDataSet.java FilteredDataSet.java
ForwardOnlyDataSet.java
Log Message:
Javadoc updates
Index: CachedDataSet.java
===================================================================
RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/dataset/CachedDataSet.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** CachedDataSet.java 10 Oct 2003 21:12:37 -0000 1.3
--- CachedDataSet.java 18 Jan 2004 16:39:23 -0000 1.4
***************
*** 28,31 ****
--- 28,33 ----
/**
+ * Hold copy of another dataset or a consumed provider content.
+ *
* @author Manuel Laflamme
* @since Apr 18, 2003
***************
*** 40,47 ****
--- 42,55 ----
private List _activeRowList;
+ /**
+ * Default constructor.
+ */
public CachedDataSet()
{
}
+ /**
+ * Creates a copy of the specified dataset.
+ */
public CachedDataSet(IDataSet dataSet) throws DataSetException
{
***************
*** 55,58 ****
--- 63,69 ----
}
+ /**
+ * Creates a CachedDataSet that syncronously consume the specified producer.
+ */
public CachedDataSet(IDataSetProducer producer) throws DataSetException
{
Index: CompositeDataSet.java
===================================================================
RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/dataset/CompositeDataSet.java,v
retrieving revision 1.12
retrieving revision 1.13
diff -C2 -d -r1.12 -r1.13
*** CompositeDataSet.java 9 Apr 2003 22:52:08 -0000 1.12
--- CompositeDataSet.java 18 Jan 2004 16:39:23 -0000 1.13
***************
*** 1,4 ****
/*
! * CompositeDataSet.java Feb 19, 2002
*
* The DbUnit Database Testing Framework
--- 1,4 ----
/*
! * CompositeDataSet.java
*
* The DbUnit Database Testing Framework
***************
*** 27,32 ****
--- 27,35 ----
/**
+ * Combines multiple datasets into a single logical dataset.
+ *
* @author Manuel Laflamme
* @version $Revision$
+ * @since Feb 19, 2002
*/
public class CompositeDataSet extends AbstractDataSet
Index: FilteredDataSet.java
===================================================================
RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/dataset/FilteredDataSet.java,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** FilteredDataSet.java 9 Aug 2003 11:23:21 -0000 1.14
--- FilteredDataSet.java 18 Jan 2004 16:39:23 -0000 1.15
***************
*** 27,31 ****
/**
! * Decorates a dataset and exposes only some tables from it.
*
* @see ITableFilter
--- 27,32 ----
/**
! * Decorates a dataset and exposes only some tables from it. Can be used with
! * different filtering strategies.
*
* @see ITableFilter
***************
*** 44,48 ****
/**
* Creates a FilteredDataSet that decorates the specified dataset and
! * exposes only the specified tables. Use the {@link SequenceTableFilter} as
* filtering startegy.
*/
--- 45,49 ----
/**
* Creates a FilteredDataSet that decorates the specified dataset and
! * exposes only the specified tables using {@link SequenceTableFilter} as
* filtering startegy.
*/
Index: ForwardOnlyDataSet.java
===================================================================
RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/dataset/ForwardOnlyDataSet.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** ForwardOnlyDataSet.java 13 Apr 2003 02:40:10 -0000 1.1
--- ForwardOnlyDataSet.java 18 Jan 2004 16:39:23 -0000 1.2
***************
*** 22,25 ****
--- 22,27 ----
/**
+ * Decorator that allows forward only access to decorated dataset.
+ *
* @author Manuel Laflamme
* @since Apr 9, 2003
|
|
From: <mla...@us...> - 2004-01-18 16:39:26
|
Update of /cvsroot/dbunit/dbunit/src/java/org/dbunit/database In directory sc8-pr-cvs1:/tmp/cvs-serv29943/src/java/org/dbunit/database Modified Files: DatabaseDataSet.java QueryDataSet.java Log Message: Javadoc updates Index: DatabaseDataSet.java =================================================================== RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/database/DatabaseDataSet.java,v retrieving revision 1.25 retrieving revision 1.26 diff -C2 -d -r1.25 -r1.26 *** DatabaseDataSet.java 13 Aug 2003 04:28:02 -0000 1.25 --- DatabaseDataSet.java 18 Jan 2004 16:39:23 -0000 1.26 *************** *** 1,4 **** /* ! * DatabaseDataSet.java Feb 17, 2002 * * The DbUnit Database Testing Framework --- 1,4 ---- /* ! * DatabaseDataSet.java * * The DbUnit Database Testing Framework *************** *** 43,48 **** --- 43,52 ---- /** + * provides access + to a database instance as a dataset. + * @author Manuel Laflamme * @version $Revision$ + * @since Feb 17, 2002 */ public class DatabaseDataSet extends AbstractDataSet Index: QueryDataSet.java =================================================================== RCS file: /cvsroot/dbunit/dbunit/src/java/org/dbunit/database/QueryDataSet.java,v retrieving revision 1.6 retrieving revision 1.7 diff -C2 -d -r1.6 -r1.7 *** QueryDataSet.java 16 Sep 2003 12:24:08 -0000 1.6 --- QueryDataSet.java 18 Jan 2004 16:39:23 -0000 1.7 *************** *** 37,40 **** --- 37,42 ---- /** + * Holds collection of tables resulting from database query. + * * @author Eric Pugh * @since December 4, 2002 |
Update of /cvsroot/dbunit/dbunit/xdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv29102/xdocs
Modified Files:
anttask.xml bestpractices.xml changes.xml faq.fml
navigation.xml properties.xml
Removed Files:
download.xml support.xml
Log Message:
More doc updates for upcomming DbUnit 2.0
Index: anttask.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/anttask.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** anttask.xml 15 Jan 2004 03:11:27 -0000 1.3
--- anttask.xml 17 Jan 2004 23:27:31 -0000 1.4
***************
*** 15,21 ****
<table border="1">
<tr>
! <td><b>Attribute</b></td>
! <td><b>Description</b></td>
! <td><b>Required</b></td>
</tr>
<tr>
--- 15,21 ----
<table border="1">
<tr>
! <th>Attribute</th>
! <th>Description</th>
! <th>Required</th>
</tr>
<tr>
***************
*** 78,84 ****
<table border="1">
<tr>
! <td><b>Attribute</b></td>
! <td><b>Description</b></td>
! <td><b>Required</b></td>
</tr>
<tr>
--- 78,84 ----
<table border="1">
<tr>
! <th>Attribute</th>
! <th>Description</th>
! <th>Required</th>
</tr>
<tr>
***************
*** 107,111 ****
</td>
</tr>
! <!--
<tr>
<td>composite</td>
<td>
<p>Use nested <a class="code"><composite></a> operation elements
to combine multiple <a class="code"><operation></a>s (on the
same file) into a single one.</p>
<table border="1">
<tr>
<td><b>Attribute</b></td>
<td><b>Description</b></td>
<td><b>Required</b></td>
</tr>
<tr>
<td>src</td>
<td>The xml source upon which the operation is to be performed</td>
<td>Yes</td>
</tr>
<tr>
<td>flat</td>
<td>If true, use <a class="code">FlatXmlDataSet</a> type in the
supplied src file. Otherwise use <a class="code">XmlDataSet</a>.
Defaults to <a class="code">true</a></td>
<td>
<p>No</p>
</td>
</tr>
</table>
<h4>Parameters specified as nested elements </h4>
<table border="1">
<tr>
<td>operation</td>
<td>See above definition for details. The src and flat attributes
are supplied as attributes to the <a class="code"><composite></a>
step and should not be attempted to be overridden by the nested
<a class="code"><operation></a> step.</td>
</tr>
</table>
</td>
</tr>
-->
<tr>
<td>export</td>
--- 107,111 ----
</td>
</tr>
! <!--
<tr>
<td>composite</td>
<td>
<p>Use nested <a class="code"><composite></a> operation elements
to combine multiple <a class="code"><operation></a>s (on the
same file) into a single one.</p>
<table border="1">
<tr>
<th>Attribute</th>
<th>Description</th>
<th>Required</th>
</tr>
<tr>
<td>src</td>
<td>The xml source upon which the operation is to be performed</td>
<td>Yes</td>
</tr>
<tr>
<td>flat</td>
<td>If true, use <a class="code">FlatXmlDataSet</a> type in the
supplied src file. Otherwise use <a class="code">XmlDataSet</a>.
Defaults to <a class="code">true</a></td>
<td>
<p>No</p>
</td>
</tr>
</table>
<h4>Parameters specified as nested elements </h4>
<table border="1">
<tr>
<td>operation</td>
<td>See above definition for details. The src and flat attributes
are supplied as attributes to the <a class="code"><composite></a>
step and should not be attempted to be overridden by the nested
<a class="code"><operation></a> step.</td>
</tr>
</table>
</td>
</tr>
-->
<tr>
<td>export</td>
***************
*** 120,126 ****
<table width="100%" border="1">
<tr>
! <td><b>Attribute</b></td>
! <td><b>Description</b></td>
! <td><b>Required</b></td>
</tr>
<tr>
--- 120,126 ----
<table width="100%" border="1">
<tr>
! <th>Attribute</th>
! <th>Description</th>
! <th>Required</th>
</tr>
<tr>
***************
*** 148,154 ****
<table border="1">
<tr>
! <td><b>Attribute</b></td>
! <td><b>Description</b></td>
! <td><b>Required</b></td>
</tr>
<tr>
--- 148,154 ----
<table border="1">
<tr>
! <th>Attribute</th>
! <th>Description</th>
! <th>Required</th>
</tr>
<tr>
***************
*** 167,173 ****
<table border="1">
<tr>
! <td><b>Attribute</b></td>
! <td><b>Description</b></td>
! <td><b>Required</b></td>
</tr>
<tr>
--- 167,173 ----
<table border="1">
<tr>
! <th>Attribute</th>
! <th>Description</th>
! <th>Required</th>
</tr>
<tr>
Index: bestpractices.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/bestpractices.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** bestpractices.xml 17 Jan 2004 04:41:40 -0000 1.3
--- bestpractices.xml 17 Jan 2004 23:27:31 -0000 1.4
***************
*** 3,8 ****
<h3>Best Practices</h3>
<ol>
! <li><a href="#onedbperdev">One database instance per developer</a></li>
! <li><a href="#nocleanup">Setup for each test does not require cleanup</a></li>
<li><a href="#smalldatasets">Use multiple small datasets </a></li>
<li><a href="#staledata">Perform setup of stale data once for entire test
--- 3,8 ----
<h3>Best Practices</h3>
<ol>
! <li><a href="#onedbperdev">Use one database instance per developer</a></li>
! <li><a href="#nocleanup">Good setup don't need cleanup!</a></li>
<li><a href="#smalldatasets">Use multiple small datasets </a></li>
<li><a href="#staledata">Perform setup of stale data once for entire test
***************
*** 10,26 ****
<li><a href="#connections">Connection management strategies</a></li>
</ol>
! <h3><a name="onedbperdev">One database instance per developer</a></h3>
<p>Testing can be simplified if you can get your database in a known state
before a test is run. A database should only be used for one test at a time;
otherwise the database state cannot be guarantied. </p><p>
So multiple developers working on the same project should have their own
! database instance to prevent data corruption.
</p>
! <h3><a name="nocleanup">Setup for each test does not require cleanup</a></h3>
<p>
! You should avoid creating tests that depends on results of preceding tests;
! this is the main purpose of DbUnit anyway. If you always put your database in
! a known state before each test execution, you don't need to do clean up at the
! end of a test. This simplifies your tests and reduces the cleanup overhead at the same time. </p>
<h3><a name="smalldatasets"> Use multiple small datasets</a></h3>
<p>
--- 10,36 ----
<li><a href="#connections">Connection management strategies</a></li>
</ol>
! <h3><a name="onedbperdev">Use one database instance per developer</a></h3>
<p>Testing can be simplified if you can get your database in a known state
before a test is run. A database should only be used for one test at a time;
otherwise the database state cannot be guarantied. </p><p>
So multiple developers working on the same project should have their own
! database instance to prevent data corruption. This also simplifies database
! cleanup, as you don't necessarily need needs to revert it to its initial state.
</p>
! <h3><a name="nocleanup">Good setup don't need cleanup!</a></h3>
<p>
! You should always avoid creating tests that depends on results of preceding
! tests; thankfully this is the main purpose of DbUnit.
! </p>
! <p>
! Don't be afraid to leave your trace after a test; principally if you are using
! <a href="#onedbperdev">one database instance per developer</a>. If you always put
! your database in a known state before a test execution, you usually don't need to
! clean it up.. This simplifies your tests maintenance and
! reduces the overhead taken by the cleanup procedure.
! And sometimes, this is very helpful to manually verify the database state after
! executing a test that fails.
! </p>
!
<h3><a name="smalldatasets"> Use multiple small datasets</a></h3>
<p>
Index: changes.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/changes.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** changes.xml 17 Jan 2004 04:41:40 -0000 1.4
--- changes.xml 17 Jan 2004 23:27:31 -0000 1.5
***************
*** 8,17 ****
<body>
<release version="1.5.6" date="October 5, 2003">
! <action dev="" type="fix" issue="786543">
<a href="http://sourceforge.net/tracker/index.php?func=detail&aid=786543&group_id=47439&atid=449491">786543</a> - NULL primitive values incorrectly returned as zero (0).
</action>
<action dev="" type="fix">
! Not NULL Oracle CLOB values incorrectly returned as NULL. </action>
</release>
<release version="1.5.5" date="July 16, 2003">
--- 8,77 ----
<body>
+ <release version="2.0" date="January ?, 2004" description="Major release.">
+ <action dev="" type="update">
+ DbUnit is now build with Maven!
+ </action>
+ <action dev="" type="update">
+ Use SAX2 instead of Electric XML parser. DbUnit has no dependencies anymore on exml.jar and dtdparser.jar.
+ </action>
+ <action dev="" type="update">
+ Dramatic memory usage improvements to get rid of the infamous OutOfMemoryError. Need some setup to take advantage of some of them. See FAQ (TODO!).
+ </action>
+ <action dev="" type="add">
+ Flat XML dataset validation.
+ </action>
+ <action dev="" type="add">
+ New <code>ITableIterator</code> interface used to iterate thru dataset tables. Allows usage of efficient lazy tables initialization for some dataset implementations. The <code>IDataSet.getTables</code> method have been deprecated and should not be used anymore.
+ </action>
+ <action dev="" type="add">
+ <code>StreamingDataSet</code>. Provides high performance and memory friendly flat XML loading.
+ </action>
+ <action dev="" type="update">
+ Global System properties are not supported anymore. You must now use the new <code>DatabaseConfig</code> object to alter DbUnit behaviours.
+ </action>
+ <action dev="" type="add">
+ New configurable DataType factory to easily integrates new custom data type with the DbUnit core. Multiple factory implementations available for some database vendors. Submit your own!
+ </action>
+ <action dev="" type="add">
+ Oracle TIMESTAMP data type support via the <code>OracleDataTypeFactory</code>.
+ </action>
+ <action dev="" type="fix">
+ Fix truncated Oracle DATE. Must use the <code>OracleDataTypeFactory</code>.
+ </action>
+ <action dev="" type="fix">
+ Fix for Oracle CLOB greater than 4000 bytes. Must use the <code>OracleDataTypeFactory</code>.
+ </action>
+ <action dev="" type="add">
+ MySQL 'longtext' data type support via the <code>MySqlDataTypeFactory</code>.
+ </action>
+ <action dev="" type="add">
+ DB2 XML data types support via the <code>Db2DataTypeFactory</code>.
+ </action>
+ <action dev="" type="add">
+ Database views support.
+ </action>
+ <action dev="" type="add">
+ New pluggable filter strategies for <code>DataSetFilter</code>. You can now exclude/include tables using wildcard patterns.
+ </action>
+ <action dev="" type="add">
+ Ability to sort tables by their dependencies with the new <code>DatabaseSequenceFilter</code> strategy.
+ </action>
+ <action dev="" type="add">
+ New <code>ReplacementDataSet</code> decorator, which can replace decorated dataset values on the fly. Can be used as a new way to specify null values for flat XML dataset.
+ </action>
+ <action dev="" type="add">
+ New <code>XlsDataSet</code>. An MS Excel dataset implementation. Uses the Jakarta POI package.
+ </action>
+ <action dev="" type="update">
+ <code>Assertion.assertEquals</code> is now performing typed comparison instead of string representation comparison.
+ </action>
+ </release>
+
<release version="1.5.6" date="October 5, 2003">
! <action dev="" type="fix">
<a href="http://sourceforge.net/tracker/index.php?func=detail&aid=786543&group_id=47439&atid=449491">786543</a> - NULL primitive values incorrectly returned as zero (0).
</action>
<action dev="" type="fix">
! Fix Oracle CLOB values incorrectly returned as NULL. </action>
</release>
<release version="1.5.5" date="July 16, 2003">
***************
*** 20,24 ****
</action>
<action dev="" type="update">
! Better handling of the various data types in general. <B>WARNING!</B> New abstract methods have been added to the DataType class. This change may break your environment if you have implemented your own data types.
</action>
<action dev="" type="update">
--- 80,89 ----
</action>
<action dev="" type="update">
! Better handling of the various data types in general. <B>WARNING!</B> New abstract methods have been
! added to the DataType class. This change may break your environment if you have implemented your
! own data types.
! </action>
! <action dev="" type="update">
! More efficient XmlDataSet writing. Now put values in CData block only when necessary.
</action>
<action dev="" type="update">
***************
*** 106,109 ****
--- 171,178 ----
<release version="1.4" date="July 17, 2002">
+ <action dev="" type="add">
+ <strong><em>DbUnitTask</em></strong> for Ant contributed by Timothy
+ Ruppert and Ben Cox.
+ </action>
<action dev="" type="update">
Moved the Base64 class to the <a class="code">org.dbunit.util</a>
***************
*** 134,141 ****
</action>
<action dev="" type="add">
- <strong><em>DbUnitTask</em></strong> for Ant contributed by Timothy
- Ruppert and Ben Cox.
- </action>
- <action dev="" type="add">
Added support for BLOB and CLOB data types.
</action>
--- 203,206 ----
***************
*** 147,153 ****
Binary data is persisted in xml datasets using the base64 encoding scheme.
</action>
- <action dev="" type="add">
- Added the CaseInsentiveDataSet class.
- </action>
<action dev="" type="update">
Deprecated the DataSetUtils.assertEquals() methods. You should now
--- 212,215 ----
***************
*** 173,177 ****
</a> document.
</action>
! <action dev="" type="update">
Removed element <none/> from dataset.dtd. This feature was incompatible
with future support for the binary data types.
--- 235,239 ----
</a> document.
</action>
! <action dev="" type="remove">
Removed element <none/> from dataset.dtd. This feature was incompatible
with future support for the binary data types.
***************
*** 189,193 ****
<release version="1.2" date="March 15, 2002">
<action dev="" type="add">
! Added the flat xml dataset format. See the <a href="components.html#FlatXmlDataSet">FlatXmlDataSet</a>
in Core Components document.
</action>
--- 251,255 ----
<release version="1.2" date="March 15, 2002">
<action dev="" type="add">
! Added the flat XML dataset format. See the <a href="components.html#FlatXmlDataSet">FlatXmlDataSet</a>
in Core Components document.
</action>
Index: faq.fml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/faq.fml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** faq.fml 17 Jan 2004 04:41:40 -0000 1.4
--- faq.fml 17 Jan 2004 23:27:31 -0000 1.5
***************
*** 7,14 ****
<faq id="supportedvendors">
<question>
! Which database system are supported?
</question>
<answer>
! <p>The Dbunit framework has been developed and tested with Oracle and HypersonicSQL.
It uses a fairly simple SQL syntax and should be compatible with the other
database systems. <a href="support.html">Let us know</a> if you find any
--- 7,14 ----
<faq id="supportedvendors">
<question>
! Which relational database systems are supported?
</question>
<answer>
! <p>The Dbunit framework is actively developed and tested with Oracle and HypersonicSQL.
It uses a fairly simple SQL syntax and should be compatible with the other
database systems. <a href="support.html">Let us know</a> if you find any
***************
*** 16,19 ****
--- 16,59 ----
</answer>
</faq>
+
+ <faq id="build">
+ <question>
+ How to build DbUnit?
+ </question>
+ <answer>
+ <p>DbUnit is build with <a href="http://maven.apache.org/">Maven 1.0-rc1</a>. The default goal will build the DbUnit jar.</p>
+ </answer>
+ </faq>
+
+ <faq id="p6spy">
+ <question>
+ How to see SQL statements issued by DbUnit using P6Spy?
+ </question>
+ <answer>
+ <p><a href="http://www.p6spy.com">P6Spy</a> is a trasparent JDBC proxy-driver
+ specialized to log the statements performed against the actual driver you normally would use.
+ Using p6spy would allow to log the SQL statements issued by DbUnit.
+ </p>
+ <p>To install P6Spy, complete the following steps:
+ <ol>
+ <li>Put the p6spy.jar file in your classpath.
+ </li><li>Move spy.properties into a directory listed in your classpath. Unlike
+ JAR files, you do not directly reference your property file in the
+ classpath (e.g.: if you have the file c:\r\proj\confspy.properties make sure you
+ put c:\r\proj\conf in the classpath).
+ </li><li>Modify your application to use the P6Spy database driver i.e.
+ com.p6spy.engine.spy.P6SpyDriver.
+ </li><li>Modify the realdriver line in the spy.properties file to reflect the
+ wrapped database driver. An example of a modified realdriver line follows:
+ realdriver = oracle.jdbc.driver.OracleDriver
+ </li></ol>
+ Installation is complete. When you run your application, a spy.log file is
+ generated in the same directory from where you run the application.
+ The log file contains a list of all of the database statements
+ executed. You can change both the destination of spy.log and what it logs by
+ editing the spy.properties file.</p>
+ </answer>
+ </faq>
+
</part>
***************
*** 112,143 ****
</faq>
! <faq id="p6spy">
<question>
! How to see SQL statements issued by DbUnit using P6Spy?
</question>
<answer>
! <p><cite>p6spy</cite> is a trasparent JDBC proxy-driver
! specialized to log the statements performed against the actual driver you normally would use.
! Using p6spy would allow to log the SQL statements issued by DbUnit.
! See more at (<a href="http://www.p6spy.com">www.p6spy.com</a>). It could be useful to stick with version 1.1
! as 1.2 as some reported minor problems.</p>
! <p>To install P6Spy, complete the following steps:
! <ol>
! <li>Put the p6spy.jar file in your classpath.
! </li><li>Move spy.properties into a directory listed in your classpath. Unlike
! JAR files, you do not directly reference your property file in the
! classpath (e.g.: if you have the file c:\r\proj\confspy.properties make sure you
! put c:\r\proj\conf in the classpath).
! </li><li>Modify your application to use the P6Spy database driver i.e.
! com.p6spy.engine.spy.P6SpyDriver.
! </li><li>Modify the realdriver line in the spy.properties file to reflect the
! wrapped database driver. An example of a modified realdriver line follows:
! realdriver = oracle.jdbc.driver.OracleDriver
! </li></ol>
! Installation is complete. When you run your application, a spy.log file is
! generated in the same directory from where you run the application.
! The log file contains a list of all of the database statements
! executed. You can change both the destination of spy.log and what it logs by
! editing the spy.properties file.</p>
</answer>
</faq>
--- 152,196 ----
</faq>
! <faq id="views">
<question>
! Can I use DbUnit with views or with synonyms?
</question>
<answer>
! <p>
! Yes. By default DbUnit is configured to only recognize normal tables. Modify the
! <a href="properties.html#tabletype">table type property</a> to work with other table types.
! </p>
! <p>
! For example, use <code>{"TABLE", "VIEW"}</code> for views and <code>{"TABLE", "SYNONYM"}</code> for synonyms.
! </p>
!
! </answer>
! </faq>
!
! <faq id="dateformat">
! <question>
! What are the dates formats used by XML dataset implementations?
! </question>
! <answer>
! <p>DbUnit use the JDBC escape formats for string representation.
! <table border="1">
! <tr>
! <th>Type</th>
! <th>Format</th>
! </tr>
! <tr>
! <td>DATE</td>
! <td>yyyy-mm-dd</td>
! </tr>
! <tr>
! <td>TIME</td>
! <td>hh:mm:ss</td>
! </tr>
! <tr>
! <td>TIMESTAMP</td>
! <td>yyyy-mm-dd hh:mm:ss.fffffffff</td>
! </tr>
! </table>
! </p>
</answer>
</faq>
***************
*** 197,205 ****
same name and located in different schemas.</p>
<p>You can solve this problem in three different ways:
! <ul>
! <li>1. Provide the schema name when creating the database connection.</li>
! <li>2. Ensure that the connection is restricted to access only one schema.</li>
! <li>3. Enable the <a href="properties.html#qualifiedtablenames">qualified table names</a> feature.</li>
! </ul>
</p>
</answer>
--- 250,258 ----
same name and located in different schemas.</p>
<p>You can solve this problem in three different ways:
! <ol>
! <li>Provide the schema name when creating the database connection.</li>
! <li>Ensure that the connection is restricted to access only one schema.</li>
! <li>Enable the <a href="properties.html#qualifiedtablenames">qualified table names</a> feature.</li>
! </ol>
</p>
</answer>
Index: navigation.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/navigation.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** navigation.xml 17 Jan 2004 04:41:40 -0000 1.5
--- navigation.xml 17 Jan 2004 23:27:31 -0000 1.6
***************
*** 11,29 ****
</links>
<menu name="Quick Links">
! <item name="About DbUnit" href="/index.html"/>
! <item name="Download" href="/download.html"/>
! <item name="FAQ" href="/faq.html"/>
<item name="Changes" href="/changes-report.html"/>
! <item name="Mailling Lists" href="/mail-lists.html"/>
<item name="Source" href="/cvs-usage.html"/>
- <item name="JavaDocs" href="apidocs/index.html"/>
</menu>
<menu name="Overview">
<item name="Database Testing" href="/intro.html"/>
<item name="Getting Started" href="/howto.html"/>
<item name="Core Components" href="/components.html"/>
<item name="Properties" href="/properties.html"/>
<item name="Ant Task" href="/anttask.html"/>
! <item name="Best Practices" href="/bestpractices.html"/>
<item name="Resources" href="/resources.html"/>
</menu>
--- 11,29 ----
</links>
<menu name="Quick Links">
! <item name="Download" href="http://sourceforge.net/project/showfiles.php?group_id=47439&release_id=189117"/>
<item name="Changes" href="/changes-report.html"/>
! <item name="FAQ" href="/faq.html"/>
! <item name="Get Support" href="https://sourceforge.net/support/getsupport.php?group_id=47439"/>
<item name="Source" href="/cvs-usage.html"/>
</menu>
<menu name="Overview">
+ <item name="About DbUnit" href="/index.html"/>
<item name="Database Testing" href="/intro.html"/>
<item name="Getting Started" href="/howto.html"/>
+ <item name="Best Practices" href="/bestpractices.html"/>
<item name="Core Components" href="/components.html"/>
<item name="Properties" href="/properties.html"/>
<item name="Ant Task" href="/anttask.html"/>
! <item name="JavaDocs" href="apidocs/index.html"/>
<item name="Resources" href="/resources.html"/>
</menu>
Index: properties.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/properties.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** properties.xml 15 Jan 2004 03:11:27 -0000 1.3
--- properties.xml 17 Jan 2004 23:27:31 -0000 1.4
***************
*** 83,86 ****
--- 83,110 ----
</tr>
</table>
+
+ <h4><a name="tabletype">Table Type</a></h4>
+ <table border="1">
+ <tr>
+ <td>Property ID</td>
+ <td>http://www.dbunit.org/properties/tableType</td>
+ </tr>
+ <tr>
+ <td>Type</td>
+ <td>String[]</td>
+ </tr>
+ <tr>
+ <td>Description</td>
+ <td>Used to configure the list of table types recognized by DbUnit.
+ See <a href="http://java.sun.com/j2se/1.3/docs/api/java/sql/DatabaseMetaData.html#getTables(java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String%5B%5D)">java.sql.DatabaseMetaData.getTables</a>
+ for possible values.</td>
+ </tr>
+ <tr>
+ <td>Default</td>
+ <td>String[]{"TABLE"}</td>
+ </tr>
+ </table>
+
+
<h4>DataType factory</h4>
<table border="1">
--- download.xml DELETED ---
--- support.xml DELETED ---
|
|
From: <mla...@us...> - 2004-01-17 23:27:34
|
Update of /cvsroot/dbunit/dbunit/src/test/org/dbunit
In directory sc8-pr-cvs1:/tmp/cvs-serv29102/src/test/org/dbunit
Modified Files:
Main.java
Log Message:
More doc updates for upcomming DbUnit 2.0
Index: Main.java
===================================================================
RCS file: /cvsroot/dbunit/dbunit/src/test/org/dbunit/Main.java,v
retrieving revision 1.33
retrieving revision 1.34
diff -C2 -d -r1.33 -r1.34
*** Main.java 12 Jan 2004 02:12:10 -0000 1.33
--- Main.java 17 Jan 2004 23:27:31 -0000 1.34
***************
*** 31,40 ****
--- 31,45 ----
import java.io.Reader;
import java.io.Writer;
+ import java.sql.Connection;
import org.dbunit.database.IDatabaseConnection;
+ import org.dbunit.database.DatabaseConfig;
+ import org.dbunit.database.ForwardOnlyResultSetTableFactory;
+ import org.dbunit.database.DatabaseConnection;
import org.dbunit.dataset.DataSetException;
import org.dbunit.dataset.IDataSet;
import org.dbunit.dataset.stream.MockDataSetProducer;
import org.dbunit.dataset.stream.StreamingDataSet;
+ import org.dbunit.dataset.stream.IDataSetProducer;
import org.dbunit.dataset.excel.XlsDataSet;
import org.dbunit.dataset.xml.FlatXmlDataSet;
***************
*** 42,45 ****
--- 47,53 ----
import org.dbunit.dataset.xml.XmlDataSet;
import org.dbunit.dataset.xml.XmlDataSetWriter;
+ import org.dbunit.dataset.xml.FlatXmlProducer;
+
+ import org.xml.sax.InputSource;
/**
***************
*** 140,145 ****
--- 148,171 ----
// }
+ public void test() throws Exception
+ {
+ Connection jdbcConnection = null;
+ IDatabaseConnection connection = new DatabaseConnection(jdbcConnection, "");
+ DatabaseConfig config = connection.getConfig();
+
+ // Use the ForwardOnlyResultSetTableFactory to export very large dataset.
+ config.setProperty(DatabaseConfig.PROPERTY_RESULTSET_TABLE_FACTORY,
+ new ForwardOnlyResultSetTableFactory());
+
+ // Use the StreamingDataSet to import very large dataset.
+ IDataSetProducer producer = new FlatXmlProducer(
+ new InputSource("dataset.xml"));
+ IDataSet dataSet = new StreamingDataSet(producer);
+ }
+
+
private static void oldMain() throws Exception
{
+
// System.setProperty("dbunit.name.escapePattern", "\"?\"");
IDatabaseConnection connection =
|
|
From: <mla...@us...> - 2004-01-17 23:27:34
|
Update of /cvsroot/dbunit/dbunit
In directory sc8-pr-cvs1:/tmp/cvs-serv29102
Modified Files:
project.xml
Log Message:
More doc updates for upcomming DbUnit 2.0
Index: project.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/project.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -d -r1.13 -r1.14
*** project.xml 17 Jan 2004 04:42:30 -0000 1.13
--- project.xml 17 Jan 2004 23:27:31 -0000 1.14
***************
*** 207,221 ****
--- 207,229 ----
-->
<report>maven-changes-plugin</report>
+ <!--
<report>maven-changelog-plugin</report>
<report>maven-file-activity-plugin</report>
<report>maven-developer-activity-plugin</report>
+ -->
<report>maven-javadoc-plugin</report>
+ <!--
<report>maven-jxr-plugin</report>
+ -->
<report>maven-junit-report-plugin</report>
+ <!--
<report>maven-tasklist-plugin</report>
<report>maven-pmd-plugin</report>
+ -->
<report>maven-faq-plugin</report>
+ <!--
<report>maven-clover-plugin</report>
<report>maven-jcoverage-plugin</report>
+ -->
</reports>
|
|
From: <mla...@us...> - 2004-01-17 04:42:33
|
Update of /cvsroot/dbunit/dbunit
In directory sc8-pr-cvs1:/tmp/cvs-serv26692
Modified Files:
project.xml
Log Message:
Finished restructuring the existing documentation for maven but new features are not document yet!
Index: project.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/project.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -C2 -d -r1.12 -r1.13
*** project.xml 15 Jan 2004 03:11:27 -0000 1.12
--- project.xml 17 Jan 2004 04:42:30 -0000 1.13
***************
*** 17,21 ****
<!-- details about the organization that 'owns' the project -->
<organization>
! <name>SourceForge</name>
<url>http://www.sourceforge.net/projects/dbunit</url>
<logo>http://sourceforge.net/sflogo.php?group_id=47439&type=5</logo>
--- 17,21 ----
<!-- details about the organization that 'owns' the project -->
<organization>
! <name>DbUnit.org</name>
<url>http://www.sourceforge.net/projects/dbunit</url>
<logo>http://sourceforge.net/sflogo.php?group_id=47439&type=5</logo>
***************
*** 25,29 ****
<inceptionYear>2002</inceptionYear>
<package>org.dbunit</package>
! <logo>http://www.dbunit.org/images/logo.jpg</logo>
<description>
DbUnit is a JUnit extension (also usable from Ant) targeted for database-driven projects that,
--- 25,29 ----
<inceptionYear>2002</inceptionYear>
<package>org.dbunit</package>
! <logo>/images/dbunit-logo.jpg</logo>
<description>
DbUnit is a JUnit extension (also usable from Ant) targeted for database-driven projects that,
***************
*** 79,82 ****
--- 79,90 ----
<developers>
<developer>
+ <name>Benjamin Cox</name>
+ <id>bdrum</id>
+ <roles>
+ <role>Java Developer</role>
+ <!-- <role>Original Ant Task Contributor</role> -->
+ </roles>
+ </developer>
+ <developer>
<name>David Eric Pugh</name>
<id>dep4b</id>
***************
*** 86,89 ****
--- 94,99 ----
<role>Java Developer</role>
</roles>
+ </developer>
+ <developer>
<name>Federico Spinazzi</name>
<id>fspinazzi</id>
***************
*** 92,95 ****
--- 102,124 ----
<roles>
<role>Java Developer</role>
+ <!-- <role>DB2 Contributor</role> -->
+ </roles>
+ </developer>
+ <developer>
+ <name>Manuel Laflamme</name>
+ <id>mlaflamm</id>
+ <email>mla...@us...</email>
+ <organization>Oz Communication</organization>
+ <roles>
+ <role>Project Founder</role>
+ <!-- <role>Java Developer</role> -->
+ </roles>
+ </developer>
+ <developer>
+ <name>Timothy J. Ruppert</name>
+ <id>zieggy</id>
+ <roles>
+ <role>Java Developer</role>
+ <!-- <role>Original Ant Task Contributor</role> -->
</roles>
</developer>
***************
*** 119,126 ****
--- 148,157 ----
<version>1.7.1</version>
</dependency>
+ <!--
<dependency>
<id>servletapi</id>
<version>2.3</version>
</dependency>
+ -->
<dependency>
<id>poi</id>
***************
*** 162,168 ****
<resources>
<resource>
! <directory>${basedir}/src/conf</directory>
<includes>
! <include>*.properties</include>
</includes>
</resource>
--- 193,199 ----
<resources>
<resource>
! <directory>${basedir}/src/java</directory>
<includes>
! <include>**/dataset.dtd</include>
</includes>
</resource>
|
Update of /cvsroot/dbunit/dbunit/xdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv26575/xdocs
Modified Files:
bestpractices.xml changes.xml components.xml download.xml
faq.fml index.xml intro.xml navigation.xml
Log Message:
Finished restructuring the existing documentation for maven but new features are not document yet!
Index: bestpractices.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/bestpractices.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** bestpractices.xml 12 Jan 2004 02:14:35 -0000 1.2
--- bestpractices.xml 17 Jan 2004 04:41:40 -0000 1.3
***************
*** 1,26 ****
<?xml version="1.0" encoding="ISO-8859-1"?>
<document><properties><title>The Dbunit Framework - Best Practices</title></properties><body><section>
! <h2>Best Practices</h2>
! <p>All existing JUnit best practices still apply to the Dbunit framework.
! Here is a collection of best practices specifically related to database
! testing and Dbunit.</p>
! <ul>
! <li><a href="#onedbperdev">Use one database copy per developer</a></li>
! <li><a href="#nocleanup">Good setup for every tests do not require cleanup</a></li>
<li><a href="#smalldatasets">Use multiple small datasets </a></li>
<li><a href="#staledata">Perform setup of stale data once for entire test
! class or a test suite</a></li>
<li><a href="#connections">Connection management strategies</a></li>
! <li><a href="#tableseq">Table sequence in dataset</a></li>
! </ul>
! <h3><a name="onedbperdev">Use one database copy per developer</a></h3>
! <p>See <a href="intro.html">introduction.</a></p>
! <h3><a name="nocleanup"> Good setup for every tests do not require cleanup</a></h3>
<p>
! People versed in testcase design already know that a test should never depend
! on results from previous tests. If you always correctly initialize your
! database before each test you won't need to do any clean up at all after
! execution.
! </p>
<h3><a name="smalldatasets"> Use multiple small datasets</a></h3>
<p>
--- 1,26 ----
<?xml version="1.0" encoding="ISO-8859-1"?>
<document><properties><title>The Dbunit Framework - Best Practices</title></properties><body><section>
! <h3>Best Practices</h3>
! <ol>
! <li><a href="#onedbperdev">One database instance per developer</a></li>
! <li><a href="#nocleanup">Setup for each test does not require cleanup</a></li>
<li><a href="#smalldatasets">Use multiple small datasets </a></li>
<li><a href="#staledata">Perform setup of stale data once for entire test
! class or test suite</a></li>
<li><a href="#connections">Connection management strategies</a></li>
! </ol>
! <h3><a name="onedbperdev">One database instance per developer</a></h3>
! <p>Testing can be simplified if you can get your database in a known state
! before a test is run. A database should only be used for one test at a time;
! otherwise the database state cannot be guarantied. </p><p>
! So multiple developers working on the same project should have their own
! database instance to prevent data corruption.
! </p>
! <h3><a name="nocleanup">Setup for each test does not require cleanup</a></h3>
<p>
! You should avoid creating tests that depends on results of preceding tests;
! this is the main purpose of DbUnit anyway. If you always put your database in
! a known state before each test execution, you don't need to do clean up at the
! end of a test. This simplifies your tests and reduces the cleanup overhead at the same time. </p>
<h3><a name="smalldatasets"> Use multiple small datasets</a></h3>
<p>
***************
*** 30,34 ****
</p>
<p>
! Those chunks could roughly corresponding to logical units, or components.
This reduces the overhead caused by initializing your database for each
test. This also facilitates team development since many developers working
--- 30,34 ----
</p>
<p>
! These chunks could roughly corresponding to logical units, or components.
This reduces the overhead caused by initializing your database for each
test. This also facilitates team development since many developers working
***************
*** 36,44 ****
</p>
<p>
! For integrated testing, you can still use the CompositeDataSet implementation
! to combine multiple datasets into one at run time.
</p>
<h3><a name="staledata"> Perform setup of stale data once for entire test
! class or a test suite</a></h3>
<p>
If several tests are using the same read-only data, this data could be initialized
--- 36,44 ----
</p>
<p>
! For integrated testing, you can still use the CompositeDataSet class
! to logically combine multiple datasets into a large one at run time.
</p>
<h3><a name="staledata"> Perform setup of stale data once for entire test
! class or test suite</a></h3>
<p>
If several tests are using the same read-only data, this data could be initialized
***************
*** 47,54 ****
run your tests but also introduces more risk. <br></br>
</p>
- <p>
- This feature is not yet integrated in Dbunit but may be added in the future.
- Something likes a DatabaseTestSuite class? <br></br>
- </p>
<h3><a name="connections"> Connection management strategies</a></h3>
<p>
--- 47,50 ----
***************
*** 57,62 ****
</p>
<h4>Remote client with DatabaseTestCase</h4>
! <p>You should reuse the same connection for the entire test suite to reduce
! the overhead of creating a new connection for each test by using a singleton.
Since version 1.1, DatabaseTestCase is closing every connection in setUp()
and tearDown(). Override the closeConnection() method with an empty body
--- 53,58 ----
</p>
<h4>Remote client with DatabaseTestCase</h4>
! <p>You should try to reuse the same connection for the entire test suite to reduce
! the overhead of creating a new connection for each test.
Since version 1.1, DatabaseTestCase is closing every connection in setUp()
and tearDown(). Override the closeConnection() method with an empty body
***************
*** 64,82 ****
<h4>In-container with Cactus or JUnitEE</h4>
<p>
! If you use the in-container strategy you should use a DatabaseDataSourceConnection
! object to access the DataSource you configured for your application server.
! Jdbc connections are requested on demand from the DataSource. So you can
rely on the built-in connection pooling capability of your application server
! to achieve better performance.
<source>IDatabaseConnection connection = new DatabaseDataSourceConnection(
new InitialContext(), "jdbc/myDataSource");</source>
</p>
- <h3><a name="tableseq"> Table sequence in dataset</a></h3>
- <p>
- To prevent problems with foreign keys, tables must be sequenced appropriately
- in dataset. The framework executes INSERT, UPDATE and REFRESH operations
- using the same sequence while DELETE and DELETE_ALL are executed in reverse
- order.
- </p>
--- 60,71 ----
<h4>In-container with Cactus or JUnitEE</h4>
<p>
! If you use the in-container strategy you should use the DatabaseDataSourceConnection
! class to access the DataSource you configured for your application server.
! JDBC connections are requested on demand from the DataSource. So you can
rely on the built-in connection pooling capability of your application server
! to achieve good performance.
<source>IDatabaseConnection connection = new DatabaseDataSourceConnection(
new InitialContext(), "jdbc/myDataSource");</source>
</p>
Index: changes.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/changes.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** changes.xml 15 Jan 2004 13:40:23 -0000 1.3
--- changes.xml 17 Jan 2004 04:41:40 -0000 1.4
***************
*** 9,18 ****
<body>
<release version="1.5.6" date="October 5, 2003">
! <action dev="" type="fix">
<a href="http://sourceforge.net/tracker/index.php?func=detail&aid=786543&group_id=47439&atid=449491">786543</a> - NULL primitive values incorrectly returned as zero (0).
</action>
<action dev="" type="fix">
! Not NULL Oracle CLOB values incorrectly returned as NULL.
! </action>
</release>
<release version="1.5.5" date="July 16, 2003">
--- 9,17 ----
<body>
<release version="1.5.6" date="October 5, 2003">
! <action dev="" type="fix" issue="786543">
<a href="http://sourceforge.net/tracker/index.php?func=detail&aid=786543&group_id=47439&atid=449491">786543</a> - NULL primitive values incorrectly returned as zero (0).
</action>
<action dev="" type="fix">
! Not NULL Oracle CLOB values incorrectly returned as NULL. </action>
</release>
<release version="1.5.5" date="July 16, 2003">
Index: components.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/components.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** components.xml 15 Jan 2004 03:11:27 -0000 1.4
--- components.xml 17 Jan 2004 04:41:40 -0000 1.5
***************
*** 86,91 ****
columns declared in the DTD as table metadata. DbUnit only support external system URI.
The URI can be absolute or relative.</p>
! <p>Learn how to export your database data to this format <a href="howto.html#extract">here</a>
! and how to generate a DTD representing your database schema <a href="howto.html#generatedtd">here</a>.
Note that DbUnit does not automatically add a reference to your DTD when
you export a dataset. You must edit the output file to manually add the
--- 86,91 ----
columns declared in the DTD as table metadata. DbUnit only support external system URI.
The URI can be absolute or relative.</p>
! <p>Read how to <a href="faq.html#extract">export</a> your database data to this format
! and how to <a href="faq.html#generatedtd">generate a DTD</a> representing your database schema.
Note that DbUnit does not automatically add a reference to your DTD when
you export a dataset. You must edit the output file to manually add the
Index: download.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/download.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** download.xml 15 Jan 2004 03:11:27 -0000 1.3
--- download.xml 17 Jan 2004 04:41:40 -0000 1.4
***************
*** 2,11 ****
<document><properties><title>The Dbunit Framework - Download</title></properties><body><section>
<h3>Download</h3>
! <p>The current Dbunit release is version 1.5.6. The distribution archive
! contains the compiled classes, the java code and the java API documentation.</p>
! <p><a href="http://sourceforge.net/project/showfiles.php?group_id=47439&release_id=189117">Download
! version 1.5.6</a></p>
! <p>If your are not reading this page online, please visit the <a href="http://www.dbunit.org/">online
! version</a> of this site since a more recent version of Dbunit might be
! available.</p>
</section></body></document>
\ No newline at end of file
--- 2,8 ----
<document><properties><title>The Dbunit Framework - Download</title></properties><body><section>
<h3>Download</h3>
! <p>The current Dbunit release is version 1.5.6. </p>
! <p><a href="http://sourceforge.net/project/showfiles.php?group_id=47439&release_id=189117">Download it from SourceForge.net</a></p>
! <p>If your are not reading this page online, please visit the <a href="http://www.dbunit.org/">DbUnit
! Home</a> as a more recent version might be available.</p>
</section></body></document>
\ No newline at end of file
Index: faq.fml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/faq.fml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** faq.fml 15 Jan 2004 03:11:27 -0000 1.3
--- faq.fml 17 Jan 2004 04:41:40 -0000 1.4
***************
*** 80,84 ****
<faq id="multipleschema">
<question>
! Can I work with multiple database schemas having table with the same name?
</question>
<answer>
--- 80,84 ----
<faq id="multipleschema">
<question>
! Can I work with multiple database schemas having tables with identical name?
</question>
<answer>
***************
*** 87,91 ****
</faq>
- <title>Using DbUnit</title>
<faq id="identity">
<question>
--- 87,90 ----
***************
*** 147,150 ****
--- 146,160 ----
<part id="use">
<title>Errors</title>
+
+ <faq id="tableseq">
+ <question>
+ Why I get a "Foreign keys constraint violation" error?
+ </question>
+ <answer>
+ DbUnit operations insert and update tables' rows in the same order they are found in your
+ dataset and delete are done in reverse order. You must order your tables and rows
+ appropriately in your datasets to prevent foreign keys constraint violation.
+ </answer>
+ </faq>
<faq id="clonedconnection">
***************
*** 197,213 ****
</part>
- <!--
- <part id="install">
- <title>Installation</title>
-
- <faq id="how-install">
- <question>
- How do I install Foo?
- </question>
- <answer>
- <p>some markup goes here</p>
- </answer>
- </faq>
- </part>
- -->
</faqs>
\ No newline at end of file
--- 207,209 ----
Index: index.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/index.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** index.xml 15 Jan 2004 03:11:27 -0000 1.3
--- index.xml 17 Jan 2004 04:41:40 -0000 1.4
***************
*** 19,26 ****
<p>
DbUnit has the ability to export and import your database (or specified tables) content to and
! from XML datasets. This is targeted for functional testing, so this is not the perfect tool to
! backup a huge production database.
! </p>
! <p>
DbUnit also provides assert facility to verify that your database content match some expected values.
</p>
--- 19,23 ----
<p>
DbUnit has the ability to export and import your database (or specified tables) content to and
! from XML datasets.
DbUnit also provides assert facility to verify that your database content match some expected values.
</p>
Index: intro.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/intro.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** intro.xml 15 Jan 2004 03:11:27 -0000 1.4
--- intro.xml 17 Jan 2004 04:41:40 -0000 1.5
***************
*** 43,47 ****
<p>[B]ut how do we manage the testing data in the database so that it doesn't
"mess up" live data?
! </p><h4>You need multiple databases</h4>
<p>Some thoughts: A good test set is self-sufficient and creates all the
data it needs. Testing can be simplified if you can get the database in
--- 43,47 ----
<p>[B]ut how do we manage the testing data in the database so that it doesn't
"mess up" live data?
! </p><h4>You need [multiple] databases</h4>
<p>Some thoughts: A good test set is self-sufficient and creates all the
data it needs. Testing can be simplified if you can get the database in
Index: navigation.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/navigation.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** navigation.xml 15 Jan 2004 03:11:27 -0000 1.4
--- navigation.xml 17 Jan 2004 04:41:40 -0000 1.5
***************
*** 11,15 ****
</links>
<menu name="Quick Links">
! <item name="News" href="/index.html"/>
<item name="Download" href="/download.html"/>
<item name="FAQ" href="/faq.html"/>
--- 11,15 ----
</links>
<menu name="Quick Links">
! <item name="About DbUnit" href="/index.html"/>
<item name="Download" href="/download.html"/>
<item name="FAQ" href="/faq.html"/>
|
|
From: <mla...@us...> - 2004-01-17 04:41:43
|
Update of /cvsroot/dbunit/dbunit
In directory sc8-pr-cvs1:/tmp/cvs-serv26575
Modified Files:
maven.xml
Log Message:
Finished restructuring the existing documentation for maven but new features are not document yet!
Index: maven.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/maven.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** maven.xml 9 Aug 2003 15:24:37 -0000 1.1
--- maven.xml 17 Jan 2004 04:41:40 -0000 1.2
***************
*** 8,12 ****
<preGoal name="xdoc:jelly-transform">
! <attainGoal name="html2xdoc"/>
</preGoal>
</project>
--- 8,24 ----
<preGoal name="xdoc:jelly-transform">
! <attainGoal name="faq"/>
! <attainGoal name="changes:report"/>
</preGoal>
+
+ <postGoal name="dist:build-setup">
+ <attainGoal name="copy:profile"/>
+ </postGoal>
+
+ <goal name="copy:profile">
+ <echo message="${maven.dist.src.archive.dir}"/>
+ <copy file="${basedir}/profile.properties" toDir="${maven.dist.src.archive.dir}/${maven.final.name}" />
+ </goal>
+
+
</project>
|
|
From: <mla...@us...> - 2004-01-17 04:08:26
|
Update of /cvsroot/dbunit/dbunit In directory sc8-pr-cvs1:/tmp/cvs-serv21714 Removed Files: dbunit-license.txt Log Message: Removed old license file --- dbunit-license.txt DELETED --- |
|
From: <mla...@us...> - 2004-01-17 04:07:41
|
Update of /cvsroot/dbunit/dbunit/docs/images In directory sc8-pr-cvs1:/tmp/cvs-serv21612/docs/images Removed Files: band.jpg body.gif header.jpg logo.jpg menu.gif silphid.gif upload.bat Log Message: Removed old site images --- band.jpg DELETED --- --- body.gif DELETED --- --- header.jpg DELETED --- --- logo.jpg DELETED --- --- menu.gif DELETED --- --- silphid.gif DELETED --- --- upload.bat DELETED --- |
|
From: <mla...@us...> - 2004-01-17 04:07:09
|
Update of /cvsroot/dbunit/dbunit/xdocs/images In directory sc8-pr-cvs1:/tmp/cvs-serv21577/xdocs/images Added Files: dbunit-logo.jpg Log Message: --- NEW FILE: dbunit-logo.jpg --- (This appears to be a binary file; contents omitted.) |
|
From: <mla...@us...> - 2004-01-17 04:04:48
|
Update of /cvsroot/dbunit/dbunit/xdocs/images In directory sc8-pr-cvs1:/tmp/cvs-serv21261/images Log Message: Directory /cvsroot/dbunit/dbunit/xdocs/images added to the repository |
|
From: <mla...@us...> - 2004-01-16 18:30:20
|
Update of /cvsroot/dbunit/dbunit/docs In directory sc8-pr-cvs1:/tmp/cvs-serv3877/docs Removed Files: index.html index.html.off properties.html stylesheet.css Log Message: Removed remaining old html doc files --- index.html DELETED --- --- index.html.off DELETED --- --- properties.html DELETED --- --- stylesheet.css DELETED --- |
|
From: <mla...@us...> - 2004-01-16 18:30:20
|
Update of /cvsroot/dbunit/dbunit/docs/api In directory sc8-pr-cvs1:/tmp/cvs-serv3877/docs/api Removed Files: index.html Log Message: Removed remaining old html doc files --- index.html DELETED --- |
|
From: <mla...@us...> - 2004-01-16 18:30:20
|
Update of /cvsroot/dbunit/dbunit/docs/Templates In directory sc8-pr-cvs1:/tmp/cvs-serv3877/docs/Templates Removed Files: main.dwt Log Message: Removed remaining old html doc files --- main.dwt DELETED --- |
|
From: <mla...@us...> - 2004-01-16 18:30:19
|
Update of /cvsroot/dbunit/dbunit/docs/_notes In directory sc8-pr-cvs1:/tmp/cvs-serv3877/docs/_notes Removed Files: dwSiteColumnsMe.xml Log Message: Removed remaining old html doc files --- dwSiteColumnsMe.xml DELETED --- |
|
From: <mla...@us...> - 2004-01-15 13:40:26
|
Update of /cvsroot/dbunit/dbunit/xdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv12078/xdocs
Modified Files:
changes.xml
Log Message:
Updated change history.
Index: changes.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/changes.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** changes.xml 13 Aug 2003 09:40:02 -0000 1.2
--- changes.xml 15 Jan 2004 13:40:23 -0000 1.3
***************
*** 4,10 ****
--- 4,19 ----
<title>Changes</title>
<author email="ep...@up...">Eric Pugh</author>
+ <author email="mla...@us...">Manuel Laflamme</author>
</properties>
<body>
+ <release version="1.5.6" date="October 5, 2003">
+ <action dev="" type="fix">
+ <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=786543&group_id=47439&atid=449491">786543</a> - NULL primitive values incorrectly returned as zero (0).
+ </action>
+ <action dev="" type="fix">
+ Not NULL Oracle CLOB values incorrectly returned as NULL.
+ </action>
+ </release>
<release version="1.5.5" date="July 16, 2003">
<action dev="" type="update">
***************
*** 14,19 ****
Better handling of the various data types in general. <B>WARNING!</B> New abstract methods have been added to the DataType class. This change may break your environment if you have implemented your own data types.
</action>
! <action dev="" type="add">
! New FlatXmlDataSet constructors that take an URL.
</action>
<action dev="" type="fix">
--- 23,28 ----
Better handling of the various data types in general. <B>WARNING!</B> New abstract methods have been added to the DataType class. This change may break your environment if you have implemented your own data types.
</action>
! <action dev="" type="update">
! Do not enable batched statement by default anymore. Many JDBC drivers have problems with this feature.
</action>
<action dev="" type="fix">
***************
*** 33,60 ****
</action>
</release>
! <release version="1.5.1" date="Apr 4, 2003">
<action dev="" type="fix">
! Multiple bugfixes:
! <ul>
! <li>Fixed DELETE operation that was not deleting tables in reverse order
! as expected.</li>
! <li><a href="http://sourceforge.net/tracker/index.php?func=detail&aid=712329&group_id=47439&atid=449491">712329</a>
! - setObject fails on BEA JDriver for MS-SQL.</li>
!
! <li> Fixed DbUnitTask "supportBatchStatement" flag. </li>
! </ul>
</action>
<action dev="" type="update">
! Optimizations
!
! <ul>
! <li>DbUnitTask DTD export. </li>
! <li>REFRESH operation.</li>
!
! </ul>
</action>
</release>
! <release version="1.5" date="Mar 1, 2003">
<action dev="" type="add">
<a href="http://sourceforge.net/tracker/index.php?func=detail&aid=533321&group_id=47439&atid=449491">533321</a>
--- 42,66 ----
</action>
</release>
! <release version="1.5.1" date="April 4, 2003">
<action dev="" type="fix">
! Fixed DELETE operation that was not deleting tables in reverse order
! as expected.
! </action>
! <action dev="" type="fix">
! <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=712329&group_id=47439&atid=449491">712329</a>
! - setObject fails on BEA JDriver for MS-SQL.
</action>
<action dev="" type="update">
! DbUnitTask DTD export optimization.
! </action>
! <action dev="" type="update">
! REFRESH operation optimization.
</action>
</release>
! <release version="1.5" date="March 1, 2003">
! <action dev="" type="fix">
! Multiple bugfixes.
! </action>
<action dev="" type="add">
<a href="http://sourceforge.net/tracker/index.php?func=detail&aid=533321&group_id=47439&atid=449491">533321</a>
***************
*** 73,77 ****
<action dev="" type="add">
<a href="http://sourceforge.net/tracker/index.php?func=detail&aid=684610&group_id=47439&atid=449494">590245</a>
! / <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=590245&group_id=47439&atid=449494">684610</a>
- New <a class="code">Reader</a> and <a class="code">Writers</a> methods
to read and write XML datasets. <a class="code">InputStream</a> and
--- 79,83 ----
<action dev="" type="add">
<a href="http://sourceforge.net/tracker/index.php?func=detail&aid=684610&group_id=47439&atid=449494">590245</a>
! & <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=590245&group_id=47439&atid=449494">684610</a>
- New <a class="code">Reader</a> and <a class="code">Writers</a> methods
to read and write XML datasets. <a class="code">InputStream</a> and
***************
*** 97,107 ****
</action>
- <action dev="" type="fix">
- Multiple bugfixes.
- </action>
</release>
! <release version="1.4" date="Jul 17, 2002">
<action dev="" type="update">
Moved the Base64 class to the <a class="code">org.dbunit.util</a>
--- 103,110 ----
</action>
</release>
! <release version="1.4" date="July 17, 2002">
<action dev="" type="update">
Moved the Base64 class to the <a class="code">org.dbunit.util</a>
***************
*** 135,142 ****
Ruppert and Ben Cox.
</action>
! <action dev="" type="update">
! Support for BLOB and CLOB data types.
</action>
</release>
</body>
</document>
--- 138,231 ----
Ruppert and Ben Cox.
</action>
! <action dev="" type="add">
! Added support for BLOB and CLOB data types.
</action>
</release>
+
+ <release version="1.3" date="April 4, 2002">
+ <action dev="" type="add">
+ Added support for binary data types: BINARY, VARBINARY and LONGVARBINARY.
+ Binary data is persisted in xml datasets using the base64 encoding scheme.
+ </action>
+ <action dev="" type="add">
+ Added the CaseInsentiveDataSet class.
+ </action>
+ <action dev="" type="update">
+ Deprecated the DataSetUtils.assertEquals() methods. You should now
+ use Assertion.assertEquals().
+ </action>
+ <action dev="" type="fix">
+ <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=533537&group_id=47439&atid=449491">533537</a>
+ - FlatXmlDataSet and null values.
+ </action>
+ <action dev="" type="fix">
+ <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=534757&group_id=47439&atid=449491">533537</a>
+ - Problem with single quotes.
+ </action>
+ <action dev="" type="fix">
+ <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=534810&group_id=47439&atid=449491">534810</a>
+ - Problem when primary key include all columns
+ </action>
+ </release>
+
+ <release version="1.2.4" date="March 19, 2002">
+ <action dev="" type="add">
+ Added support for multiple schemas per connection. See <a href="faq.html#multipleschema">FAQ
+ </a> document.
+ </action>
+ <action dev="" type="update">
+ Removed element <none/> from dataset.dtd. This feature was incompatible
+ with future support for the binary data types.
+ </action>
+ <action dev="" type="fix">
+ <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=530998&group_id=47439&atid=449491">530998</a>
+ - DataSetUtils.AssertEquals(ITable table, ITable table).
+ </action>
+ <action dev="" type="fix">
+ <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=533540&group_id=47439&atid=449491">533540</a>
+ - Problem with DATE, TIME and TIMESTAMP.
+ </action>
+ </release>
+
+ <release version="1.2" date="March 15, 2002">
+ <action dev="" type="add">
+ Added the flat xml dataset format. See the <a href="components.html#FlatXmlDataSet">FlatXmlDataSet</a>
+ in Core Components document.
+ </action>
+ <action dev="" type="add">
+ Added database data verification feature. See <a href="howto.html#assertdata">Getting Started</a> document.
+ </action>
+ <action dev="" type="update">
+ Updated Electric XML parser to version 3.2.
+ </action>
+ </release>
+
+ <release version="1.1" date="March 10, 2002">
+ <action dev="" type="update">
+ Connections are now closed in each setUp() and tearDown(). You
+ must override the DatabaseTestCase.closeConnection() and provide
+ an empty body to modify this behavior. This is not recommended to bypass connection close if
+ you use connection pooling.
+ </action>
+ <action dev="" type="add">
+ Added the IDatabaseConnection interface.
+ </action>
+ <action dev="" type="add">
+ Added the DatabaseDataSourceConnection class. This class provides
+ support for accessing JDBC connections from a DataSource. JDBC connections
+ are requested on demand from the DataSource.
+ </action>
+ <action dev="" type="update">
+ Multiple performance improvement.
+ </action>
+ <action dev="" type="fix">
+ <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=526235&group_id=47439&atid=449491">526235</a>
+ - Cannot export tables with JDBC-ODBC bridge and MS-SQL.
+ </action>
+ </release>
+
+ <release version="1.0" date="Febuary 27, 2002" description="Initial public release.">
+ </release>
+
</body>
</document>
|
Update of /cvsroot/dbunit/dbunit/xdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv11829/xdocs
Modified Files:
anttask.xml components.xml download.xml faq.fml howto.xml
index.xml intro.xml navigation.xml properties.xml
resources.xml
Log Message:
More xdoc reformating
Index: anttask.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/anttask.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** anttask.xml 12 Jan 2004 02:14:35 -0000 1.2
--- anttask.xml 15 Jan 2004 03:11:27 -0000 1.3
***************
*** 1,6 ****
<?xml version="1.0" encoding="ISO-8859-1"?>
<document><properties><title>The Dbunit Framework - Ant Task</title></properties><body><section>
! <h2>Ant Integration</h2>
! <h3>Installation</h3>
The steps required to add the DbUnit task to your system are:
<p>1. Add the DbUnit jar to Ant's classpath. </p>
--- 1,6 ----
<?xml version="1.0" encoding="ISO-8859-1"?>
<document><properties><title>The Dbunit Framework - Ant Task</title></properties><body><section>
! <h3>Ant Integration</h3>
! <h4>Installation</h4>
The steps required to add the DbUnit task to your system are:
<p>1. Add the DbUnit jar to Ant's classpath. </p>
Index: components.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/components.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** components.xml 14 Jan 2004 22:04:21 -0000 1.3
--- components.xml 15 Jan 2004 03:11:27 -0000 1.4
***************
*** 1,12 ****
<?xml version="1.0" encoding="ISO-8859-1"?>
! <document><properties><title>The Dbunit Framework - Framework Components</title></properties><body><section>
! <h2>Core Classes</h2>
! The following walks you through the core classes that make up DbUnit:
! <ul>
! <li><a href="#dataset">IDataSet (org.dbunit.dataset)</a></li>
! <li><a href="#databaseconnection">IDatabaseConnection (org.dbunit.database)</a></li>
! <li><a href="#databaseoperation">DatabaseOperation (org.dbunit.operation)</a></li>
! </ul>
<p>All the above are interfaces or abstract classes and you will find yourself
using implementations or subclasses.</p>
--- 1,13 ----
<?xml version="1.0" encoding="ISO-8859-1"?>
! <document><properties><title>Core Components</title></properties><body><section>
! <h3>Core Components</h3>
! <p>The following walks you through the core classes that make up DbUnit:
! <ol>
! <li><a href="#dataset">IDataSet</a></li>
! <li><a href="#databaseconnection">IDatabaseConnection</a></li>
! <li><a href="#databaseoperation">DatabaseOperation</a></li>
! </ol>
! </p>
<p>All the above are interfaces or abstract classes and you will find yourself
using implementations or subclasses.</p>
Index: download.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/download.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** download.xml 14 Jan 2004 02:03:59 -0000 1.2
--- download.xml 15 Jan 2004 03:11:27 -0000 1.3
***************
*** 1,5 ****
<?xml version="1.0" encoding="ISO-8859-1"?>
<document><properties><title>The Dbunit Framework - Download</title></properties><body><section>
! <h2>Download</h2>
<p>The current Dbunit release is version 1.5.6. The distribution archive
contains the compiled classes, the java code and the java API documentation.</p>
--- 1,5 ----
<?xml version="1.0" encoding="ISO-8859-1"?>
<document><properties><title>The Dbunit Framework - Download</title></properties><body><section>
! <h3>Download</h3>
<p>The current Dbunit release is version 1.5.6. The distribution archive
contains the compiled classes, the java code and the java API documentation.</p>
Index: faq.fml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/faq.fml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** faq.fml 14 Jan 2004 03:44:38 -0000 1.2
--- faq.fml 15 Jan 2004 03:11:27 -0000 1.3
***************
*** 10,22 ****
</question>
<answer>
!
! The Dbunit framework has been developed and tested with Oracle and HypersonicSQL.
It uses a fairly simple SQL syntax and should be compatible with the other
database systems. <a href="support.html">Let us know</a> if you find any
! incompatibilities.
</answer>
</faq>
<faq id="identity">
<question>
--- 10,91 ----
</question>
<answer>
! <p>The Dbunit framework has been developed and tested with Oracle and HypersonicSQL.
It uses a fairly simple SQL syntax and should be compatible with the other
database systems. <a href="support.html">Let us know</a> if you find any
! incompatibilities.</p>
! </answer>
! </faq>
! </part>
!
! <part id="use">
! <title>Using DbUnit</title>
! <faq id="extract">
! <question>
! How to extract a flat XML dataset from my database?
! </question>
! <answer>
! <p>
! The following sample demonstrates how you can export one or many tables
! from a database to an flat XML dataset file.
! <source>
! public class DatabaseExportSample
! {
! public static void main(String[] args) throws Exception
! {
! // database connection
! Class driverClass = Class.forName("org.hsqldb.jdbcDriver");
! Connection jdbcConnection = DriverManager.getConnection(
! "jdbc:hsqldb:sample", "sa", "");
! IDatabaseConnection connection = new DatabaseConnection(jdbcConnection);
!
! // partial database export
! String[] tableNames = {"TABLE1", "TABLE2", "TABLE2"};
! IDataSet partialDataSet = connection.createDataSet(tableNames);
! FlatXmlDataSet.write(partialDataSet, new FileOutputStream("partial.xml"));
!
! // full database export
! IDataSet fullDataSet = connection.createDataSet();
! FlatXmlDataSet.write(fullDataSet, new FileOutputStream("full.xml"));
! }
! }</source></p> </answer>
! </faq>
!
! <faq id="generatedtd">
! <question>
! How to generate a DTD representing my database schema?
! </question>
! <answer>
! <p>The following sample demonstrates how you can generate a flat xml dataset
! DTD from a database.</p>
! <source>
! public class DatabaseExportSample
! {
! public static void main(String[] args) throws Exception
! {
! // database connection
! Class driverClass = Class.forName("org.hsqldb.jdbcDriver");
! Connection jdbcConnection = DriverManager.getConnection(
! "jdbc:hsqldb:sample", "sa", "");
! IDatabaseConnection connection = new DatabaseConnection(jdbcConnection);
!
! // write DTD file
! FlatDtdDataSet.write(connection.createDataSet(),
! new FileOutputStream("test.dtd"));
! }
! }</source>
!
! </answer>
! </faq>
+ <faq id="multipleschema">
+ <question>
+ Can I work with multiple database schemas having table with the same name?
+ </question>
+ <answer>
+ Yes, see the <a href="properties.html#qualifiedtablenames">qualified table names</a> feature.
</answer>
</faq>
+ <title>Using DbUnit</title>
<faq id="identity">
<question>
***************
*** 29,38 ****
specific. If your database does not provide a way to disable this feature
then you are out of luck and DbUnit cannot be used with it. </p>
! <p>Since version 1.4, DbUnit support IDENTITY columns for MS SQL Server
with the class <a href="components.html#IdentityInsertOperation">IdentityInsertOperation</a>.
- <br></br>
</p>
</answer>
</faq>
<faq id="clonedconnection">
--- 98,150 ----
specific. If your database does not provide a way to disable this feature
then you are out of luck and DbUnit cannot be used with it. </p>
! <p>DbUnit support IDENTITY columns for MS SQL Server
with the class <a href="components.html#IdentityInsertOperation">IdentityInsertOperation</a>.
</p>
</answer>
</faq>
+
+ <faq id="flatxmlnull">
+ <question>
+ How to specify NULL values with flat XML dataset?
+ </question>
+ <answer>
+ <p>See <a href="components.html#FlatXmlDataSet">FlatXmlDataSet documentation</a></p>
+ </answer>
+ </faq>
+
+ <faq id="p6spy">
+ <question>
+ How to see SQL statements issued by DbUnit using P6Spy?
+ </question>
+ <answer>
+ <p><cite>p6spy</cite> is a trasparent JDBC proxy-driver
+ specialized to log the statements performed against the actual driver you normally would use.
+ Using p6spy would allow to log the SQL statements issued by DbUnit.
+ See more at (<a href="http://www.p6spy.com">www.p6spy.com</a>). It could be useful to stick with version 1.1
+ as 1.2 as some reported minor problems.</p>
+ <p>To install P6Spy, complete the following steps:
+ <ol>
+ <li>Put the p6spy.jar file in your classpath.
+ </li><li>Move spy.properties into a directory listed in your classpath. Unlike
+ JAR files, you do not directly reference your property file in the
+ classpath (e.g.: if you have the file c:\r\proj\confspy.properties make sure you
+ put c:\r\proj\conf in the classpath).
+ </li><li>Modify your application to use the P6Spy database driver i.e.
+ com.p6spy.engine.spy.P6SpyDriver.
+ </li><li>Modify the realdriver line in the spy.properties file to reflect the
+ wrapped database driver. An example of a modified realdriver line follows:
+ realdriver = oracle.jdbc.driver.OracleDriver
+ </li></ol>
+ Installation is complete. When you run your application, a spy.log file is
+ generated in the same directory from where you run the application.
+ The log file contains a list of all of the database statements
+ executed. You can change both the destination of spy.log and what it logs by
+ editing the spy.properties file.</p>
+ </answer>
+ </faq>
+ </part>
+
+ <part id="use">
+ <title>Errors</title>
<faq id="clonedconnection">
***************
*** 46,53 ****
in the JDBC connection string (as outlined by <a href="http://forum.java.sun.com/thread.jsp?forum=48&thread=184797">this
JDC thread</a>). Your database Url would look something like the following:
! </p>
! <p>
! <pre>jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=mydb;SelectMethod=cursor
! </pre>
</p>
</answer>
--- 158,162 ----
in the JDBC connection string (as outlined by <a href="http://forum.java.sun.com/thread.jsp?forum=48&thread=184797">this
JDC thread</a>). Your database Url would look something like the following:
! <source>jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=mydb;SelectMethod=cursor</source>
</p>
</answer>
***************
*** 77,127 ****
that it is getting columns information from multiple tables having the
same name and located in different schemas.</p>
! <p>You can solve this problem in three different ways:<br></br>
! 1. Provide the schema name when creating the database connection.<br></br>
! 2. Ensure that the connection is restricted to access only one schema.<br></br>
! 3. Use fully qualified table names as specified <a href="howto.html#multipleschema">here</a>.<br></br>
</p>
</answer>
</faq>
- <faq id="flatxmlnull">
- <question>
- How to specify NULL values with flat XML dataset
- </question>
- <answer>
- <p>See FlatXmlDataSet documentation <a href="components.html#FlatXmlDataSet">here</a>.</p>
- </answer>
- </faq>
-
- <faq id="p6spy">
- <question>
- How to see SQL statements issued by DbUnit using P6Spy?
- </question>
- <answer>
- <p><cite>p6spy</cite> is a trasparent JDBC proxy-driver
- specialized to log the statements performed against the actual driver you normally would use.
- Using p6spy would allow to log the SQL statements issued by DbUnit.
- See more at (<a href="http://www.p6spy.com">www.p6spy.com</a>). It could be useful to stick with version 1.1
- as 1.2 as some reported minor problems.</p>
- <p>To install P6Spy, complete the following steps:
- <ol>
- <li>Put the p6spy.jar file in your classpath.
- </li><li>Move spy.properties into a directory listed in your classpath. Unlike
- JAR files, you do not directly reference your property file in the
- classpath (e.g.: if you have the file c:\r\proj\confspy.properties make sure you
- put c:\r\proj\conf in the classpath).
- </li><li>Modify your application to use the P6Spy database driver i.e.
- com.p6spy.engine.spy.P6SpyDriver.
- </li><li>Modify the realdriver line in the spy.properties file to reflect the
- wrapped database driver. An example of a modified realdriver line follows:
- realdriver = oracle.jdbc.driver.OracleDriver
- </li></ol>
- Installation is complete. When you run your application, a spy.log file is
- generated in the same directory from where you run the application.
- The log file contains a list of all of the database statements
- executed. You can change both the destination of spy.log and what it logs by
- editing the spy.properties file.</p>
- </answer>
- </faq>
</part>
<!--
--- 186,199 ----
that it is getting columns information from multiple tables having the
same name and located in different schemas.</p>
! <p>You can solve this problem in three different ways:
! <ul>
! <li>1. Provide the schema name when creating the database connection.</li>
! <li>2. Ensure that the connection is restricted to access only one schema.</li>
! <li>3. Enable the <a href="properties.html#qualifiedtablenames">qualified table names</a> feature.</li>
! </ul>
</p>
</answer>
</faq>
</part>
<!--
Index: howto.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/howto.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** howto.xml 13 Aug 2003 09:40:02 -0000 1.1
--- howto.xml 15 Jan 2004 03:11:27 -0000 1.2
***************
*** 1,39 ****
<?xml version="1.0" encoding="ISO-8859-1"?>
! <document><properties><title>The Dbunit Framework - Howto Guides</title></properties><body><section> <h2>How-to Guides</h2>
! <ul>
! <li><a href="#createtest">How to create a test case to setup your database</a></li>
! <li><a href="#noextend">How to setup your database in a test case that
! does not extend DatabaseTestCase</a></li>
! <li><a href="#extract">How to export a dataset from your database</a></li>
! <li><a href="#generatedtd">How to generate a DTD representing your database
! schema</a></li>
! <li><a href="#assertdata">How to verify that your database contains expected
! data</a> <font color="#FF0000">(updated)</font></li>
! <li><a href="#multipleschema">How to export data from or import data to
! multiple database schemas</a></li>
! <li><a href="#canoo">How to Use DbUnit with Canoo WebTest </a> <font color="#FF0000">(new)</font></li>
! </ul>
! <hr></hr>
<a name="createtest">
! <h2>How to create a test case to setup your database</h2>
! </a> To write a test case, please follow the steps described below.<br></br>
! <br></br>
! <h4>Step 1: Create your dataset file</h4>
! Your test will obviously need some data to work with. This means you must
create a dataset. In most situations you will work with xml datasets. You
! can manually create an xml dataset from scratch or create one by exporting
! some data from your database (see <a href="#extract">how-to export</a>).<br></br>
! <br></br>
<h4>Step 2: Extend the DatabaseTestCase class</h4>
! Now you need to create a test class. The easiest way to use Dbunit is to
make your test class extend the DatabaseTestCase class. DatabaseTestCase
extends the JUnit TestCase class. Two template methods are required to be
implemented: <a class="code">getConnection()</a> to return a connection
to your database and <a class="code">getDataSet()</a> to return the dataset
! you created in step 1.<br></br>
! <br></br>
Following is a sample implementation that returns a connection to a Hypersonic
! database and an xml dataset:<br></br>
! <pre>
public class SampleTest extends DatabaseTestCase
{
--- 1,38 ----
<?xml version="1.0" encoding="ISO-8859-1"?>
! <document><properties><title>Getting Started</title></properties><body><section>
! <h3>Getting Started</h3>
! <ol><li><a href="#createtest">
! Database setup with DatabaseTestCase subclass
! </a></li>
! <li><a href="#noextend">
! Database setup with your own TestCase subclass
! </a></li>
! <li><a href="#assertdata">
! Database data verification
! </a></li>
! <li><a href="#canoo">
! DbUnit Ant task and Canoo WebTest
! </a></li></ol>
<a name="createtest">
! <h3>Database setup with DatabaseTestCase subclass</h3>
! </a>
! <a name="createdataset"><h4>Step 1: Create your dataset file</h4></a>
! <p>Your test need some data to work with. This means you must
create a dataset. In most situations you will work with xml datasets. You
! can manually create a <a href="components.html#FlatXmlDataSet">flat XML dataset</a>
! from scratch or create one by <a href="faq.html#extract">exporting</a>
! some data from your database.
! </p>
<h4>Step 2: Extend the DatabaseTestCase class</h4>
! <p>Now you need to create a test class. The easiest way to use Dbunit is to
make your test class extend the DatabaseTestCase class. DatabaseTestCase
extends the JUnit TestCase class. Two template methods are required to be
implemented: <a class="code">getConnection()</a> to return a connection
to your database and <a class="code">getDataSet()</a> to return the dataset
! you created in step 1.</p>
! <p>
Following is a sample implementation that returns a connection to a Hypersonic
! database and an xml dataset:
! <source>
public class SampleTest extends DatabaseTestCase
{
***************
*** 55,60 ****
return new FlatXmlDataSet(new FileInputStream("dataset.xml"));
}
! }</pre>
! <br></br>
<h4>Step 3: (Optional) Implement getSetUpOperation() and getTearDownOperation()
methods</h4>
--- 54,59 ----
return new FlatXmlDataSet(new FileInputStream("dataset.xml"));
}
! }</source>
! </p>
<h4>Step 3: (Optional) Implement getSetUpOperation() and getTearDownOperation()
methods</h4>
***************
*** 64,70 ****
and <a class="code">getTearDownOperation()</a>.</p>
<p>The following example demonstrates how you can easily override the operation
! executed before or after your test.<br></br>
! </p>
! <pre>
public class SampleTest extends DatabaseTestCase
{
--- 63,68 ----
and <a class="code">getTearDownOperation()</a>.</p>
<p>The following example demonstrates how you can easily override the operation
! executed before or after your test.
! <source>
public class SampleTest extends DatabaseTestCase
{
***************
*** 80,98 ****
}
...
! }</pre>
<h4>Step 4: Implement your testXXX() methods</h4>
! Implement your test methods as you normally would with JUnit. Your database
is now initialized before and cleaned-up after each test methods according
! to what you did in previous steps.<br></br>
! <br></br>
<a name="noextend">
! <h2>How to setup your database in a test case that does not extend DatabaseTestCase</h2>
! </a> In order to use Dbunit you are not required to extend the DatabaseTestCase
! class. Simply override the standard JUnit setUp() method and execute the
desired operation on your database. Do something similar in teardown() if
! you need to perform any clean-up.<br></br>
! <br></br>
! For example:<br></br>
! <pre>
public class SampleTest extends TestCase
{
--- 78,99 ----
}
...
! }</source>
! </p>
<h4>Step 4: Implement your testXXX() methods</h4>
! <p>Implement your test methods as you normally would with JUnit. Your database
is now initialized before and cleaned-up after each test methods according
! to what you did in previous steps.</p>
<a name="noextend">
!
!
! <h3>Database setup with your own TestCase subclass</h3>
! </a>
! <p>In order to use Dbunit you are not required to extend the DatabaseTestCase
! class. You can override the standard JUnit setUp() method and execute the
desired operation on your database. Do something similar in teardown() if
! you need to perform clean-up.</p>
! <p>
! For example:
! <source>
public class SampleTest extends TestCase
{
***************
*** 124,196 ****
}
...
! }</pre>
! <a name="extract">
! <h2>How to export a dataset from your database</h2>
! </a> Since version 1.2, the <a href="components.html#FlatXmlDataSet">flat
! XML dataset</a> format is the prefered way to persist a dataset in XML.
! The following sample demonstrates how you can export one or many tables
! from a database to an flat XML dataset file.<br></br>
! <pre>
! public class DatabaseExportSample
! {
! public static void main(String[] args) throws Exception
! {
! // database connection
! Class driverClass = Class.forName("org.hsqldb.jdbcDriver");
! Connection jdbcConnection = DriverManager.getConnection(
! "jdbc:hsqldb:sample", "sa", "");
! IDatabaseConnection connection = new DatabaseConnection(jdbcConnection);
!
! // partial database export
! String[] tableNames = {"TABLE1", "TABLE2", "TABLE2"};
! IDataSet partialDataSet = connection.createDataSet(tableNames);
! FlatXmlDataSet.write(partialDataSet, new FileOutputStream("partial.xml"));
!
! // full database export
! IDataSet fullDataSet = connection.createDataSet();
! FlatXmlDataSet.write(fullDataSet, new FileOutputStream("full.xml"));
! }
! }</pre>
! <a name="generatedtd">
! <h2>How to generate a DTD representing your database schema</h2>
! </a>
! <p>The following sample demonstrates how you can generate a flat xml dataset
! DTD from a database.</p>
! <pre>
! public class DatabaseExportSample
! {
! public static void main(String[] args) throws Exception
! {
! // database connection
! Class driverClass = Class.forName("org.hsqldb.jdbcDriver");
! Connection jdbcConnection = DriverManager.getConnection(
! "jdbc:hsqldb:sample", "sa", "");
! IDatabaseConnection connection = new DatabaseConnection(jdbcConnection);
!
! // write DTD file
! FlatDtdDataSet.write(connection.createDataSet(),<br></br> new FileOutputStream("test.dtd"));<br></br> }
! }</pre>
<a name="assertdata">
! <h2>How to verify that your database contains expected data</h2>
! </a> Dbunit provides support for verifying whether two tables or datasets
! contain identical data. <br></br>
! <pre>public class Assertion
{
public static void assertEquals(ITable expected, ITable actual)
public static void assertEquals(IDataSet expected, IDataSet actual)
! }</pre>
! This can be used to verify if your database contains the expected data during
! your tests. In this case, the actual dataset is a database snapshot you
! want to verify against an expected dataset. As its name imply, the expected
! dataset contains the expectation values that usually comes from an XML file
! or have been created in memory.
! <p>The expected dataset must be different from the one you have used to
! setup your database. Therefore you need two datasets to do that; one to
! setup your database before a test and another to provide the expected
! data during the test.</p>
! <p>The following example, show how to compare a database table snapshot
! against a flat XML table:<br></br>
! </p>
! <pre>public class SampleTest extends DatabaseTestCase
{
public SampleTest(String name)
--- 125,145 ----
}
...
! }</source></p>
<a name="assertdata">
! <h3>Database data verification</h3>
! </a>
! <p>Dbunit provides support for verifying whether two tables or datasets
! contain identical data. The following two methods can be used to verify if
! your database contains the expected data during
! test cases execution.
! <source>public class Assertion
{
public static void assertEquals(ITable expected, ITable actual)
public static void assertEquals(IDataSet expected, IDataSet actual)
! }</source></p>
! <h4>Sample</h4>
! <p>The following sample, show how to compare a database table snapshot
! against a flat XML table.
! <source>public class SampleTest extends DatabaseTestCase
{
public SampleTest(String name)
***************
*** 219,239 ****
Assertion.assertEquals(expectedTable, databaseTable);
}
! }</pre>
! <h3>Verifying the result of a database query </h3>
<p>You can also verify if the result of a query match an expected set of
data. The query can be used to select only a subset of a table or even
! join multiple tables together like this:</p>
! <p>
! <pre> ITable actualJoinData = getConnection().createQueryTable("RESULT_NAME",
! "SELECT * FROM TABLE1, TABLE2 WHERE ..."); </pre>
! </p><h3>Ignoring some columns </h3>
<p>The following code snippet shows you how to ignore some columns in the
comparison. To works, the actual table MUST contain at least ALL the columns
from the expected table. Extra columns can exist in the actual table but
not in the expected one.
! </p><p>
! <pre> Assertion.assertEquals(expected,
! new CompositeTable(expected.getTableMetaData(), actual)); </pre>
! </p><h3>Row ordering</h3>
<p>By default, database table snapshot taken by DbUnit are sorted by primary
keys. If a table does not have a primary key or the primary key is automatically
--- 168,197 ----
Assertion.assertEquals(expectedTable, databaseTable);
}
! }</source> </p>
! <p>The actual dataset is a database snapshot you
! want to verify against an expected dataset. As its name imply, the expected
! dataset contains the expectation values.
! </p>
! <p>The expected dataset must be different from the one you have used to
! setup your database. Therefore you need two datasets to do that; one to
! setup your database before a test and another to provide the expected
! data during the test.</p>
!
! <a name="assertquery"><h4>Using a query to take the database snapshot</h4></a>
<p>You can also verify if the result of a query match an expected set of
data. The query can be used to select only a subset of a table or even
! join multiple tables together.
! <source> ITable actualJoinData = getConnection().createQueryTable("RESULT_NAME",
! "SELECT * FROM TABLE1, TABLE2 WHERE ..."); </source>
! </p>
! <h4>Ignoring some columns </h4>
<p>The following code snippet shows you how to ignore some columns in the
comparison. To works, the actual table MUST contain at least ALL the columns
from the expected table. Extra columns can exist in the actual table but
not in the expected one.
! <source> Assertion.assertEquals(expected,
! new CompositeTable(expected.getTableMetaData(), actual)); </source>
! </p>
! <a name="roworder"><h4>Row ordering</h4></a>
<p>By default, database table snapshot taken by DbUnit are sorted by primary
keys. If a table does not have a primary key or the primary key is automatically
***************
*** 242,272 ****
<p>You must order your database snapshot manually by using <code>IDatabaseConnection.createQueryTable</code>
with an "ORDER BY" clause. Or you can use the <code>SortedTable</code>
! decorator class like this:</p>
! <p>
! <pre> Assertion.assertEquals(new SortedTable(expected),
! new SortedTable(actual, expected.getTableMetaData()));</pre>
! <a name="multipleschema">
! </a></p><h2>How to export data from or import data to multiple database schemas</h2>
! Dbunit support multiple schemas per connection since version 1.2.3.
! To enable multiple schemas support, set the following system property before
! the creation of your database connection.
! <pre>
! System.setProperty("dbunit.qualified.table.names", "true");</pre>
! <p>This tells to Dbunit to work with table names qualified by their schema
! name. If this mode is enabled, all table names are assumed to have this
! format: SCHEMA_NAME.TABLE_NAME. <br></br>
! </p>
! <p>Example of flat xml dataset exported or imported when qualified table
! names mode is enabled:</p>
! <pre><dataset>
! <SCHEMA1.TABLE1 COLUMN0="row 0 col 0" COLUMN1="row 0 col 1"/&
! <SCHEMA1.TABLE1 COLUMN0="row 1 col 0" COLUMN1="row 1 col 1"/>
! <SCHEMA2.TABLE2 COLUMN0="row 0 col 0" COLUMN1="row 0 col 1" COLUMN2="row 0 col 2"/>
! </dataset></pre>
<a name="canoo">
! <h2>How to Use DbUnit with Canoo WebTest</h2>
</a>
<p>By Eric Pugh</p>
! <p>With Dbunit 1.4's new Ant tasks, Dbunit makes it much easier to run WebTest
scripts for database centric applications. <a href="http://webtest.canoo.com">WebTest</a>
is a tool to simulate a user's browser clicking through the pages on a
--- 200,211 ----
<p>You must order your database snapshot manually by using <code>IDatabaseConnection.createQueryTable</code>
with an "ORDER BY" clause. Or you can use the <code>SortedTable</code>
! decorator class like this:
! <source> Assertion.assertEquals(new SortedTable(expected),
! new SortedTable(actual, expected.getTableMetaData()));</source></p>
<a name="canoo">
! <h3>DbUnit Ant task and Canoo WebTest</h3>
</a>
<p>By Eric Pugh</p>
! <p>With Dbunit Ant tasks, Dbunit makes it much easier to run Canoo WebTest
scripts for database centric applications. <a href="http://webtest.canoo.com">WebTest</a>
is a tool to simulate a user's browser clicking through the pages on a
***************
*** 274,286 ****
website. In fact, this can be used to perform User Acceptance tests for
websites built using non Java technologies like ColdFusion or ASP! This
! howto walks you through a suggested format for storing tests. <br></br>
</p>
<h4>Step 1: Create your dataset file</h4>
! Your first step is to create your dataset file that you wan to load into
your database before running your WebTest script. Use one of the various
! methods described above. Put the various datasets you need in a <code>/data</code>
! directory.
<h4>Step 2: Create your Ant build.xml file</h4>
! A suggested setup is to have a single build.xml file that is the entry point
for all your tests. This would include a couple targets like:
<ol>
--- 213,225 ----
website. In fact, this can be used to perform User Acceptance tests for
websites built using non Java technologies like ColdFusion or ASP! This
! document walks you through a suggested format for storing tests.
</p>
<h4>Step 1: Create your dataset file</h4>
! <p>Your first step is to create your dataset file that you wan to load into
your database before running your WebTest script. Use one of the various
! methods <a href="#createdataset">described above</a>. Put the various datasets you need in a <code>/data</code>
! directory.</p>
<h4>Step 2: Create your Ant build.xml file</h4>
! <p>A suggested setup is to have a single build.xml file that is the entry point
for all your tests. This would include a couple targets like:
<ol>
***************
*** 288,315 ****
</li><li> <code>test:single</code>: Runs a single test in a specific testSuite
</li><li> <code>test:suite</code>: Runs all the tests for a specific testSuite
! </li></ol>
<h4>Step 3: Create your various Test Suites</h4>
! Once you have your build.xml file set up, you can now call the various TestSuites.
Create a separate TestSuiteXXX.xml for the various modules that you would
like to test. In your TestSuiteXXX.xml, you should have your default target
testSuite call all the testcases you have definied:
! <pre>
! <target name="testSuite">
! <antcall target="unsubscribeEmailAddressWithEmail"/>
! <antcall target="unsubscribeEmailAddressWithEmailID"/>
! <antcall target="unsubscribeEmailAddressWithNewEmailAddress"/>
! <antcall target="subscribeEmailAddressWithOptedOutEmail"/>
! <antcall target="subscribeEmailAddressWithNewEmailAddress"/>
! <antcall target="subscribeEmailAddressWithInvalidEmailAddress"/>
! </target>
! </pre>
! This way you can either run all the test's in your Test Suite, or just run
! a specific one, all from build.xml! <br></br>
<h4>Step 4: Create your various Tests</h4>
! Now you need to write your various testcases. For more information on WebTest,
! please refer to <a href="http://webtest.canoo.com">the WebTest</a> home page.
If you have find you are duplicating pieces of XML, then place them in a
<code>/includes</code> directory. If you have a single set of properties,
--- 227,252 ----
</li><li> <code>test:single</code>: Runs a single test in a specific testSuite
</li><li> <code>test:suite</code>: Runs all the tests for a specific testSuite
! </li></ol></p>
<h4>Step 3: Create your various Test Suites</h4>
! <p>Once you have your build.xml file set up, you can now call the various TestSuites.
Create a separate TestSuiteXXX.xml for the various modules that you would
like to test. In your TestSuiteXXX.xml, you should have your default target
testSuite call all the testcases you have definied:
! <source><![CDATA[ <target name="testSuite">
! <antcall target="unsubscribeEmailAddressWithEmail"/>
! <antcall target="unsubscribeEmailAddressWithEmailID"/>
! <antcall target="unsubscribeEmailAddressWithNewEmailAddress"/>
! <antcall target="subscribeEmailAddressWithOptedOutEmail"/>
! <antcall target="subscribeEmailAddressWithNewEmailAddress"/>
! <antcall target="subscribeEmailAddressWithInvalidEmailAddress"/>
! </target>]]></source></p>
! <p>This way you can either run all the test's in your Test Suite, or just run
! a specific one, all from build.xml!</p>
<h4>Step 4: Create your various Tests</h4>
! <p>Now you need to write your various testcases. For more information on WebTest,
! please refer to the <a href="http://webtest.canoo.com">WebTest home page</a>.
If you have find you are duplicating pieces of XML, then place them in a
<code>/includes</code> directory. If you have a single set of properties,
***************
*** 320,352 ****
into the database, and using the MSSQL_CLEAN_INSERT instead of CLEAN_INSERT
because of the requirement to do identity column inserts.
! <pre>
! <target name="subscribeEmailAddressWithOptedOutEmail">
! <dbunit
driver="${sql.jdbcdriver}"
url="${sql.url}"
userid="${sql.username}"
! password="${sql.password}">
! <operation type="MSSQL_CLEAN_INSERT"
src="data/subscribeEmailAddressWithOptedOutEmail.xml"
! format="flat"/>
! </dbunit>
! <testSpec name="subscribeEmailAddressWithOptedOutEmail">
&sharedConfiguration;
! <steps>
! <invoke stepid="main page"
url="/edm/subscribe.asp?e=s...@te..."
! save="subscribeEmailAddressWithNewEmailAddress"/>
! <verifytext stepid="Make sure we received the success message"
! text="You have been subscribed to the mailing list"/>
! </steps>
! </testSpec>
! </target>
! </pre>
! <br></br>
<h4>Sample Directory Layout</h4>
! When you are done, you will have a series of files that look like this:
! <pre>
! \root\
<a href="sample_webtest/build.xml">build.xml</a>
<a href="sample_webtest/build.properties">build.properties</a>
--- 257,286 ----
into the database, and using the MSSQL_CLEAN_INSERT instead of CLEAN_INSERT
because of the requirement to do identity column inserts.
! <source><![CDATA[ <target name="subscribeEmailAddressWithOptedOutEmail">
! <dbunit
driver="${sql.jdbcdriver}"
url="${sql.url}"
userid="${sql.username}"
! password="${sql.password}">
! <operation type="MSSQL_CLEAN_INSERT"
src="data/subscribeEmailAddressWithOptedOutEmail.xml"
! format="flat"/>
! </dbunit>
! <testSpec name="subscribeEmailAddressWithOptedOutEmail">
&sharedConfiguration;
! <steps>
! <invoke stepid="main page"
url="/edm/subscribe.asp?e=s...@te..."
! save="subscribeEmailAddressWithNewEmailAddress"/>
! <verifytext stepid="Make sure we received the success message"
! text="You have been subscribed to the mailing list"/>
! </steps>
! </testSpec>
! </target>]]></source>
! </p>
<h4>Sample Directory Layout</h4>
! <p>When you are done, you will have a series of files that look like this:
! <source> \root\
<a href="sample_webtest/build.xml">build.xml</a>
<a href="sample_webtest/build.properties">build.properties</a>
***************
*** 356,360 ****
<a href="sample_webtest/subscribeEmailAddressWithOptedOutEmail.xml">subscribeEmailAddressWithOptedOutEmail.xml</a>
\root\includes\
! <a href="sample_webtest/sharedConfiguration.xml">sharedConfiguration.xml</a>
! </pre>
</section></body></document>
\ No newline at end of file
--- 290,293 ----
<a href="sample_webtest/subscribeEmailAddressWithOptedOutEmail.xml">subscribeEmailAddressWithOptedOutEmail.xml</a>
\root\includes\
! <a href="sample_webtest/sharedConfiguration.xml">sharedConfiguration.xml</a></source></p>
</section></body></document>
\ No newline at end of file
Index: index.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/index.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** index.xml 14 Jan 2004 03:44:38 -0000 1.2
--- index.xml 15 Jan 2004 03:11:27 -0000 1.3
***************
*** 4,8 ****
<properties>
! <title>DBUnit</title>
<author email="ep...@up...">Eric Pugh</author>
</properties>
--- 4,8 ----
<properties>
! <title>About DbUnit and News</title>
<author email="ep...@up...">Eric Pugh</author>
</properties>
***************
*** 10,14 ****
<body>
! <section name="DBUnit">
<p>
DbUnit is a JUnit extension (also usable from Ant) targeted for database-driven projects that,
--- 10,14 ----
<body>
! <section name="About DbUnit">
<p>
DbUnit is a JUnit extension (also usable from Ant) targeted for database-driven projects that,
Index: intro.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/intro.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** intro.xml 14 Jan 2004 02:03:59 -0000 1.3
--- intro.xml 15 Jan 2004 03:11:27 -0000 1.4
***************
*** 1,16 ****
<?xml version="1.0" encoding="ISO-8859-1"?>
! <document><properties><title>The Dbunit Framework - Home</title></properties><body><section>
! <h2>Introduction</h2>
<p>Richard Dallaway notes about database unit testing inspired me the realization
of the DbUnit framework. I think this is a very good text about this subject.
Hopefully he gave me the permission to present excerpts from his notes
! here on the DbUnit site.</p>
<p>The original text is much longer and I strongly suggest you to read it
as well. See <a href="resources.html#RichardDallaway">resources</a> for
! reference to it.<br></br>
</p>
- <hr></hr>
<p>
! </p><h3>Unit testing database code</h3>
<p>These are my notes on how I've gone about unit testing database functionality.</p>
<p> [...]</p>
--- 1,15 ----
<?xml version="1.0" encoding="ISO-8859-1"?>
! <document><properties><title>Database Testing</title></properties><body><section>
! <h3>Database Testing</h3>
<p>Richard Dallaway notes about database unit testing inspired me the realization
of the DbUnit framework. I think this is a very good text about this subject.
Hopefully he gave me the permission to present excerpts from his notes
! here.</p>
<p>The original text is much longer and I strongly suggest you to read it
as well. See <a href="resources.html#RichardDallaway">resources</a> for
! reference to it. - Manuel Laflamme
</p>
<p>
! </p><h3>Unit testing database</h3>
<p>These are my notes on how I've gone about unit testing database functionality.</p>
<p> [...]</p>
***************
*** 19,24 ****
How can you put tests in place to make sure your code really is reading
and writing the right data from the database? </p>
! <p>
! </p><h3>Why bother?</h3>
<p>I'm guessing some, if not a lot, of database development goes like this:
set up database, write code to access database, run code, do a SELECT
--- 18,22 ----
How can you put tests in place to make sure your code really is reading
and writing the right data from the database? </p>
! <h4>Why bother?</h4>
<p>I'm guessing some, if not a lot, of database development goes like this:
set up database, write code to access database, run code, do a SELECT
***************
*** 45,49 ****
<p>[B]ut how do we manage the testing data in the database so that it doesn't
"mess up" live data?
! </p><h3>You need four databases</h3>
<p>Some thoughts: A good test set is self-sufficient and creates all the
data it needs. Testing can be simplified if you can get the database in
--- 43,47 ----
<p>[B]ut how do we manage the testing data in the database so that it doesn't
"mess up" live data?
! </p><h4>You need multiple databases</h4>
<p>Some thoughts: A good test set is self-sufficient and creates all the
data it needs. Testing can be simplified if you can get the database in
Index: navigation.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/navigation.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** navigation.xml 10 Oct 2003 10:24:32 -0000 1.3
--- navigation.xml 15 Jan 2004 03:11:27 -0000 1.4
***************
*** 7,25 ****
<body>
<links>
! <item name="SF" href="http://www.sf.net/projects/dbunit"/>
<item name="Maven Plugin" href="http://maven-plugins.sourceforge.net/maven-dbunit-plugin/index.html"/>
</links>
! <menu name="Docs">
! <item name="Overview" href="/index.html"/>
! <item name="Intro" href="/intro.html"/>
! <item name="Ant Task" href="/anttask.html"/>
! <item name="Best Practices" href="/bestpractices.html"/>
! <item name="Components" href="/components.html"/>
<item name="Download" href="/download.html"/>
<item name="FAQ" href="/faq.html"/>
! <item name="Howto" href="/howto.html"/>
<item name="Properties" href="/properties.html"/>
<item name="Resources" href="/resources.html"/>
- <item name="Support" href="/support.html"/>
</menu>
</body>
--- 7,30 ----
<body>
<links>
! <item name="SourceForge.net Project Page" href="http://www.sf.net/projects/dbunit"/>
<item name="Maven Plugin" href="http://maven-plugins.sourceforge.net/maven-dbunit-plugin/index.html"/>
</links>
! <menu name="Quick Links">
! <item name="News" href="/index.html"/>
<item name="Download" href="/download.html"/>
<item name="FAQ" href="/faq.html"/>
! <item name="Changes" href="/changes-report.html"/>
! <item name="Mailling Lists" href="/mail-lists.html"/>
! <item name="Source" href="/cvs-usage.html"/>
! <item name="JavaDocs" href="apidocs/index.html"/>
! </menu>
! <menu name="Overview">
! <item name="Database Testing" href="/intro.html"/>
! <item name="Getting Started" href="/howto.html"/>
! <item name="Core Components" href="/components.html"/>
<item name="Properties" href="/properties.html"/>
+ <item name="Ant Task" href="/anttask.html"/>
+ <item name="Best Practices" href="/bestpractices.html"/>
<item name="Resources" href="/resources.html"/>
</menu>
</body>
Index: properties.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/properties.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** properties.xml 14 Jan 2004 03:44:38 -0000 1.2
--- properties.xml 15 Jan 2004 03:11:27 -0000 1.3
***************
*** 1,5 ****
<?xml version="1.0" encoding="ISO-8859-1"?>
! <document><properties><title>The Dbunit Framework - Properties</title></properties><body><section>
! <h2>DbUnit features and properties</h2>
<p>DbUnit does not use System properties anymore since version 2.0. DbUnit
use a configuration object, <code>DatabaseConfig</code>, to query
--- 1,5 ----
<?xml version="1.0" encoding="ISO-8859-1"?>
! <document><properties><title>Configurable Features and Properties</title></properties><body><section>
! <h3>Configurable features and properties</h3>
<p>DbUnit does not use System properties anymore since version 2.0. DbUnit
use a configuration object, <code>DatabaseConfig</code>, to query
***************
*** 35,42 ****
<tr>
<td>Description</td>
! <td>Enable or disable multiple schemas support. If enabled, Dbunit access
! tables with names fully qualified by schema using this format: SCHEMA.TABLE.
! Also see <a href="howto.html#multipleschema">how to import/export
! with multiple schema</a>. </td>
</tr>
</table>
--- 35,39 ----
<tr>
<td>Description</td>
! <td>Enable or disable usage of JDBC batched statement by DbUnit. </td>
</tr>
</table>
***************
*** 54,58 ****
<tr>
<td>Description</td>
! <td>Enable or disable usage of JDBC batched statement by DbUnit. </td>
</tr>
<tr>
--- 51,56 ----
<tr>
<td>Description</td>
! <td>Enable or disable multiple schemas support. If enabled, Dbunit access
! tables with names fully qualified by schema using this format: SCHEMA.TABLE.</td>
</tr>
<tr>
Index: resources.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/xdocs/resources.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** resources.xml 14 Jan 2004 03:44:38 -0000 1.2
--- resources.xml 15 Jan 2004 03:11:27 -0000 1.3
***************
*** 1,10 ****
<?xml version="1.0" encoding="ISO-8859-1"?>
<document><properties><title>The Dbunit Framework - Ressources</title></properties><body><section>
! <h3>SourceForge Project Ressources</h3>
! <p><a href="http://sourceforge.net/projects/dbunit/">Project summary</a></p>
! <p><a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dbunit/">Browse
! CVS repository</a></p>
! <p>
! </p><h3>Other Ressources</h3>
<p>
<table border="1">
--- 1,5 ----
<?xml version="1.0" encoding="ISO-8859-1"?>
<document><properties><title>The Dbunit Framework - Ressources</title></properties><body><section>
! <h3>External Ressources</h3>
<p>
<table border="1">
|
|
From: <mla...@us...> - 2004-01-15 03:11:31
|
Update of /cvsroot/dbunit/dbunit
In directory sc8-pr-cvs1:/tmp/cvs-serv11829
Modified Files:
project.xml
Log Message:
More xdoc reformating
Index: project.xml
===================================================================
RCS file: /cvsroot/dbunit/dbunit/project.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -C2 -d -r1.11 -r1.12
*** project.xml 14 Jan 2004 03:44:38 -0000 1.11
--- project.xml 15 Jan 2004 03:11:27 -0000 1.12
***************
*** 19,23 ****
<name>SourceForge</name>
<url>http://www.sourceforge.net/projects/dbunit</url>
! <logo>http://sourceforge.net/sflogo.php?group_id=47439</logo>
</organization>
--- 19,23 ----
<name>SourceForge</name>
<url>http://www.sourceforge.net/projects/dbunit</url>
! <logo>http://sourceforge.net/sflogo.php?group_id=47439&type=5</logo>
</organization>
|
