daruma-20091130:
  * fixed a problem according to mysql max connection restriction. DaRuMa
    was not able to handle connections over mysql max connection. Now DaRuMa
    can handle over mysql max connection.

daruma-20091125:

  * changed default value of geometry index. This change causes a restriction
    that user can't register geometry with minOccurs="0".
    If you'd like to use geometry with minOccurs="0", change following line
    in daruma.property file to false.

       daruma.geometry.create_geometry_index = true


daruma-20091113:

  * fixed a bug of returning error document when user specifies unexistent
    featue types in RegisterFeatureType directive.


daruma-20091008:

  * changed --debug option to write verbose debug messages.

  * changed to check restricted geometry types such as PointPropertyType
    strictly. Now, error shall be returned if you insert unmatched geometry
    type items.

  * changed to check property list of Update command strictly. If multiple
    values are bound to one property, error shall be returned.

  * changed to disconnect all connections explicitly when received ctrl-c or
    signals.

daruma-20090924:

  * changed to update TransactionID when RegisterFeatureType or
    RegisterCoordinateSystemTransformation is executed.

  * fixed missing RegisterCoordinateSystemTransformation in response of
    GetCapabilities.


daruma-20090915:

  * fixed a bug concern with time and geometry type with minOccurs="0".
    when time or geometry items are omitted, GetFeature returned empty
    invalid form tags.

  * fixed documentation mismatch of GetFeature mode at MISP documentation and
    DaRuMa implementation.


daruma-20090909:

  * fixed Update command to be able to handle geometry and time type.
    changed to check values strictly.

  * fixed a bug concern with timezone of @_create_time_, @_update_time_.

  * updated README file to reduce ambiguity.


daruma-20090813:

  * added types to hold restricted geometry type.
    (temtative implementation, will not reject invalid child element)

        PointPropertyType
        CurvePropertyType
        LineStringPropertyType (deprecated by CurvePropertyType)
        SurfacePropertyType
        PolygonPropertyType (deprecated by SurfacePropertyType)
        MultiPointPropertyType
        MultiCurvePropertyType
        MultiLineStringPropertyType (deprecated by MultiCurvePropertyType)
        MultiSurfacePropertyType
        MultiPolygonPropertyType (deprecated by MultiSurfacePropertyType)

    Some types are deprecated. They ware defeined in GML 2, but marked
    `deprecated' by GML 3. Use types defined in GML 3 instead.


daruma-20090730:

  * fixed a bug of coordinate system translation when multiple translations
    have applied.


daruma-20090611:

  * changed to handle error information of coordinate system transformation.

  * fixed some namespacess in response of coordinate transformation
    registration.

  * changed namespace of sample data in sample-data/simple-2/.

  * added description of sample data to README.


daruma-20090528:

  * added a script for auto invoking on System V init architecture.

  * added <GetCoordinateSystemTransformation> command to protocol.
	Server shall return all of CoordinateSystemTransformation.

  * changed to be able to switch MySQL connection end point.

	If you change following lines in daruma.properties file,
	you can specify host and port which MySQL is waiting.

	        daruma.mysql.host = localhost
	        daruma.mysql.port = 3306

  * changed to be able to switch print initial message or not when
    client connects to administrator port.

  * changed to use administrator port by default.


daruma-20090421:

  * added sample data.

  * added `shutdown' command to administration protocol.
	If you execute `shutdown' via administration port,
	daruma shall block new connection and wait finish of running procedure,
	when all procedures are done, daruma shall be exit automatically.

  * fixed a bug of response of Delete.
	When Delete request issued for already deleted features,
	old version reported too many number of deleted features.


daruma-20090311:

  * changed to specify maxFeatures and startPosition attribute in <GetFeature>

	format: <GetFeature startPosition="N" maxFeatures="M">...</GetFeature>
		(N,M is positive integer)

	* `maxFeatures' specifies maximum number of features returned
	  as result of query.
	  (This feature is same as `limit' attribute of `Query'.
	   `limit' is obsoleted. Use maxFeatures instead.)

	* `startPosition' specifies offset of features to return.
		N means that server returns featurs from Nth feature.
		In other words, skips head N-1 features.
		Default Values id 1.

	If both of startPosition and maxFeatures are specified,
	server uses offset specified by startPosition and returns
	maxFeatures if exists from offset.

	You can see sample data file for testing in test/test-sortBy
	directory.


  * on Unix and Mac, changed `run' script to work correctly
     when invoked by another directory.


  * added description of SortBy, maxFeatures, startPosition and transformType
    to MISP specification.


  * this NEWS file appeared in package.
